MCP Multi-Tenant Security: How to Isolate Customer Data
A shared MCP server must never let one tenant's agent access another tenant's resources.
A shared MCP server must never let one tenant's agent access another tenant's resources.
Carry tenant context through every request and enforce ownership before tool execution.
A shared MCP server can serve many customers efficiently, but multi-tenancy introduces a critical requirement: every request must remain inside the correct tenant boundary.
The trusted application should attach tenant and user identity to the request.
Do not let the model choose an arbitrary tenant_id and treat it as proof of access.
A tool such as get_invoice should verify that the invoice belongs to the authenticated tenant.
This check should happen even if the resource ID was obtained from another trusted-looking tool.
Caching can accidentally become a cross-tenant data leak.
Cache keys should include the appropriate tenant and authorization scope.
Even within a tenant, a user may not have access to every record.
Apply row-level and field-level authorization before data reaches the model.
Create tests where a valid user attempts to reference another tenant's IDs.
Also test indirect paths: search results, cached records, error messages, logs, and tool outputs.
The MCP server should know whether a request came from an authenticated user, an agent running on behalf of that user, or a background workflow.
Do not collapse all of these identities into one shared service account without an audit trail.
Multi-tenancy must be enforced on every MCP operation.
Carry trusted identity through the request, verify resource ownership server-side, isolate caches, filter results, and test deliberate cross-tenant access attempts.
Source: multi-tenant authorization and MCP security principles.
A practical MCP deployment should keep four boundaries explicit: identity, capability, resource, and execution. Identity answers who is acting. Capability answers which tool is allowed. Resource answers which tenant, project, record, or environment can be touched. Execution controls answer how the operation is performed, including timeouts, retries, quotas, and approval requirements.
Do not rely on tool descriptions to enforce these boundaries. Descriptions help the model choose correctly, but the MCP server or trusted backend must reject unauthorized requests. This also protects the system when a prompt injection, buggy client, or compromised workflow sends an unexpected call.
For external dependencies, use bounded timeouts and classify errors. A temporary provider outage may justify a retry, while an authorization failure should stop immediately. For side effects, make duplicate execution safe with idempotency or an operation-status check before retrying.
Test valid and invalid arguments, missing permissions, cross-tenant resource IDs, revoked credentials, unavailable servers, malformed tool results, rate limits, timeouts, and cancellation. Also test what happens when retrieved content contains instructions that attempt to invoke a privileged operation.
For production systems, include integration tests that verify the full chain from authenticated user to MCP client, server policy, downstream service, and sanitized result. A successful local tool call is not enough evidence that the complete security boundary is correct.
MCP becomes valuable when it makes capabilities composable without making authority ambiguous. Keep discovery selective, permissions deterministic, identity explicit, data minimized, and execution observable.
Choose where policy lives before adding more servers. In a small product, the MCP server itself can own authorization and resource checks. In a larger system, a gateway or policy service can provide shared identity, quotas, and audit decisions while each server retains domain-specific validation. What matters is that there is one trusted enforcement path and that clients cannot bypass it.
Keep development capabilities separate from production capabilities. A developer-facing server may expose logs, database inspection, or test data that should never be discoverable by a customer-facing agent. Use separate credentials, registries, and environments where appropriate.
For long-running workflows, persist the workflow state outside the model. If an MCP server disconnects, the system should be able to resume or fail safely without asking the model to reconstruct critical authorization state from conversation history.
Plan for servers disappearing, credentials expiring, downstream APIs returning malformed data, and clients receiving stale tool definitions. A discovery failure should not silently fall back to a broader capability. A permission failure should not be converted into a generic retry. A timeout should not automatically mean that a side effect did not happen.
Use health checks, bounded retries, circuit breakers for unstable dependencies, and clear degraded states. When a tool becomes unavailable, the agent should know that capability is unavailable rather than inventing a result.
Before production, ask whether every exposed tool has a clear owner, a documented purpose, a resource boundary, a permission model, a timeout, an error contract, and an audit trail. Remove tools that are unused or whose authority cannot be explained precisely.
The goal is not the largest MCP tool catalog. The goal is a small set of capabilities that an agent can use predictably and that engineers can explain during a security review.
Start with one read-only server and a small allowlist of tools. Measure discovery, execution latency, denied calls, errors, and successful task completion. Once the read path is stable, add one carefully scoped write operation with an approval requirement. Only then consider broader integrations.
This staged approach makes failures easier to isolate and keeps the blast radius small. It also creates useful evidence for deciding which tools deserve permanent access. Remove capabilities that provide little value relative to their security and maintenance cost.
Can a tool access a resource outside the current tenant? Can retrieved content influence a privileged operation? Can a retry duplicate a side effect? Can an expired credential remain usable? Can a client discover a production-only capability? Can an error reveal sensitive data? Can one compromised server reach unrelated internal systems?
If any answer is unclear, the integration is not finished. Make the boundary explicit in code, tests, and documentation before expanding the tool set.
Community
0 comments
React to this article
Trending now
Written by
Kirtesh Admute
Founder
Kirtesh Admute is the founder of IndieFounder, a platform for founders, builders, and people curious about technology. He writes about AI, startups, software, product building, and the lessons that come from building in public.
See an issue with this story?
