Known routes
Register each protected MCP server as a route.
Control agentic sprawl
A route, identity, and tool-policy inventory for MCP
Manage MCP servers as Pomerium routes. Assign user or service-account identities, apply route policy, and limit named MCP tools.
What this pattern controls
Known callers
Give every caller a user or service identity.
Known tools
Limit exact tool names and patterns.
Route inventory
Organize MCP servers as protected routes
Treat each MCP server as a Pomerium route. Organize route policy in the control plane for the selected edition.
- Attach policy to each MCP route.
- Use Enterprise namespaces for inherited policy when required.
- Use the Zero hosted control plane to manage Zero routes and policy.
Governance boundary
Assign known identities and limit the tool surface
Give each caller a known identity, then limit the named tools that identity can call. This boundary does not filter application records or response fields.
- Use an interactive user, a unique service account, or an impersonating service account.
- Use exact tool-name deny rules or an allowlist.
- Use upstream OAuth when each user needs a separate hosted-service connection.
Technical sources
MCP overview
Protect and organize MCP server routes.
Limit MCP tool calling
Block exact tool names, patterns, or all but an allowlist.
MCP with upstream OAuth
Manage a separate upstream OAuth connection for each user.
