MCP Server BAA Requirements for PHI: Self-Hosted vs Vendor-Hosted Deployments
A Business Associate Agreement is needed when a party outside the covered entity creates, receives, maintains or transmits PHI on its behalf. A self-hosted MCP server run by the covered entity does not usually create a new business associate, but the data platform vendor and any model provider that receives PHI in tool results still need to be assessed. A vendor-hosted MCP server that handles PHI generally makes its operator a business associate. A BAA is necessary in those cases but does not satisfy the technical safeguards. Counsel should confirm each determination.
Safeguards and evidence that remain regardless of BAA status
- Server inventory: operator, location, connected systems and the PHI each can reach, reviewed whenever a connector is added.
- Access control: a distinct identity for each user or agent, with connector permissions scoped to the task and not to the whole repository, site or schema.
- Minimum necessary: limits on which fields, files and row counts a tool call may return, applied before data reaches the model.
- Transmission security: protected transport on every hop, including server to platform and server to model.
- Audit controls under 164.312(b): a record of each tool call that retrieves PHI, covering requester, target, scope of data returned and outcome, retained and reviewable.
- Contract review: BAAs for each party that handles PHI, including subcontractor arrangements, with counsel confirming each determination.
The BAA test is about relationships, not technology
HHS states that the HIPAA Rules permit a covered entity to disclose PHI to a business associate if it obtains satisfactory assurances, in a contract or other written arrangement, that the business associate will appropriately safeguard the information. HHS also states that whether a BAA is required depends on the relationship between the parties. Nothing in that framing turns on whether the component is called an MCP server, an API gateway or a plugin.
It follows that an MCP server should be treated as a data-path component. For each one, record who operates it, where it runs, and what PHI it can reach. Then ask whether the operator creates, receives, maintains or transmits PHI for the covered entity. If an outside party does, that party is a candidate business associate, and the BAA must describe permitted and required uses and disclosures and provide that PHI will not be used or further disclosed other than as permitted by the agreement or by law.
The same test applies one hop further. HHS notes that BAA requirements also run between business associates and their subcontractors. A vendor-hosted MCP server that relays results to another service pulls that service into the analysis.
How deployment model changes who needs coverage
In a self-hosted deployment, the MCP server runs inside the covered entity's own environment and is operated by its own staff. PHI moves from the data platform to the MCP server within the entity's boundary, so the server operator is not an outside party. No separate BAA for the MCP server follows from that alone. The obligations do not disappear, however. The covered entity still owns access control, minimum necessary and audit controls for the server, and any outside party on the other side of the path still has to be assessed.
In a vendor-hosted deployment, the vendor runs the server and PHI passes through infrastructure the covered entity does not operate. If the vendor can receive, store, cache or transmit PHI while serving tool calls, it is generally acting as a business associate, and a BAA covering that specific hosted service is needed before PHI flows. Subprocessors used by the vendor become subcontractor relationships that the vendor's own agreements must address.
The model provider is a separate question that deployment choice does not settle. If tool results containing PHI are placed into a hosted model's context, the model provider receives PHI and needs its own assessment, whether the MCP server is self-hosted or vendor-hosted. If results stay within a model the covered entity runs in its own environment, that hop does not leave the boundary.
Connector by connector: where PHI sits and what changes
The four connectors differ mainly in how PHI is stored and how broadly a tool call can reach it. The platform vendor's agreement with the covered entity is a separate matter from the MCP server operator's status. Each platform's BAA coverage should be confirmed for the specific service in use.
- SharePoint: PHI sits in unstructured documents and lists, often outside folders anyone labeled as clinical. Self-hosted: the server acts inside the entity's boundary with delegated or service permissions, so the main risk is over-broad site access. Vendor-hosted: document content and tokens pass through the vendor, which makes the operator a likely business associate and adds a subprocessor chain to trace.
- Google Drive: PHI lives in shared files and folders whose sharing settings may be wider than intended. Self-hosted: the entity controls where credentials and fetched content reside. Vendor-hosted: file content is transmitted through vendor infrastructure, so the hosted service needs BAA coverage and the platform's own BAA scope should be checked against Drive.
- Postgres: PHI sits in structured tables, and a tool call can return rows at scale. Self-hosted: queries stay inside the network, and database role design determines minimum necessary. Vendor-hosted: the vendor needs network reach and credentials to the database, and result rows transit its systems. Where the database itself runs on a managed host, that host is a further party to assess.
- Snowflake: PHI is concentrated in analytic tables where one query can span many patients. Self-hosted: the server connects under a narrowly scoped role, and result sets are bounded by that role. Vendor-hosted: warehouse credentials and query results pass through the vendor, so credential scope and result size limits matter as much as the contract.
Evaluating a vendor-hosted MCP server offering
Start with whether the vendor will sign a BAA that covers the specific hosted MCP service, not only its other products. Compare the draft against what HHS says a BAA must contain, in particular the permitted and required uses and disclosures and the prohibition on further use or disclosure.
Then trace the data flows. Ask which subprocessors and model providers can receive PHI, whether agreements exist down the chain, how long request and response content is retained, and where it is stored. These are the points where a hosted service can maintain PHI without the covered entity noticing.
Finally, ask what evidence the vendor can produce. Business associates are directly liable for certain HIPAA provisions, and the technical safeguards in 164.312 apply to them as well as to covered entities. The covered entity still needs per-call records showing which identity requested what, which data was returned, and what policy applied. A vendor that cannot produce those records leaves a gap that the contract does not close.
A BAA is necessary but not sufficient
A BAA allocates responsibility and sets permitted uses. It does not decide, at the moment of a tool call, what an MCP server may read or return. A contract cannot redact a diagnosis from a result or block a query that exceeds the minimum necessary. Those decisions have to be made at runtime, and the record of what happened has to be kept as evidence.
This is where policy enforcement in the execution path applies. Trussed enforces policy on MCP tool calls at runtime, with allow, redact and block decisions, and generates audit-ready evidence of each interaction, mapped to HIPAA. It deploys self-managed in the customer cloud, with configurable retention and data residency, and runs in production with healthcare organizations.
One caution on timing. A proposed update to the Security Rule was published in January 2025. As of November 2026, it should not be treated as current requirements. The existing 164.312 safeguards are the operative standard.
Parties in the MCP data path to test for BAA coverage
Covered entity
Owns the PHI and the AI assistant or agent that requests it.
MCP server operator
Runs the connector that retrieves and returns data. Either the covered entity or a vendor.
Data platform vendor
Hosts SharePoint, Drive, Postgres or Snowflake content where PHI is maintained.
Model provider
Receives tool results if they are passed into a hosted model.
Map your MCP connectors to BAA and safeguard requirements
Talk through your SharePoint, Drive, Postgres and Snowflake deployments and see how runtime enforcement and audit-ready evidence work for MCP tool calls.
Explore Agent and Tool-Call Enforcement