Contain the agent, sheet 04 of 13
One governed pipe between agents and tools: which servers exist, who may call which tool, and what was called.
Ask every gateway what it does when no policy is configured. Get a data-flow diagram for each hop before regulated data touches a tool.
← → move to the next sheet over, Esc zooms out.
MCP is the plug standard that lets an agent use tools: your issue tracker, your database, your email. Plug in a few and it feels like magic. Plug in fifty and nobody can say which agent called what, as whom, about which customer.
A gateway is the building's front desk. Every visitor signs in, gets a badge for the floors they're allowed on, and the desk keeps the log. Without it, every server in the building has its own unlocked side door.
Cloud vendors, API-gateway companies and startups all sell a gateway now, and open-source ones are free. They differ most in the boring parts: what happens when no policy is set, what gets logged, and whose identity rides on each call.
Every link opened on 11 Nov 2026. The numbers match the squares on the map.
Standard
The current revision of the protocol, with its changes from the last one: no protocol-level sessions, a required Mcp-Method header on every request, and Mcp-Name on tool, resource and prompt calls.
The catch. Revisions break things. Pin the revision your gateway and your servers support.
Open source, community
A community-driven registry service for discovering MCP servers, with a public API.
The catch. Still a preview, and the project warns that breaking changes or data resets may occur. It lists servers. It doesn't vet them.
Open source, MIT
Runs MCP servers in containers behind one gateway, with Docker's catalog of ready-made servers.
The catch. A gateway you run is a gateway you patch. Check what it allows before a policy is in place.
Open source, MIT
An open-source platform for managing MCP servers, with a gateway that is one governed entry point to every server a user may reach.
The catch. It's a platform, not a drop-in proxy. Budget time to run it.
Open source, MIT
A reverse proxy and management layer for MCP servers, with session-aware routing and lifecycle management, built for Kubernetes.
The catch. Infrastructure to operate, aimed at teams already running Kubernetes.
Product
A managed MCP and LLM gateway, formerly MintMCP: approved servers in role-based bundles, tool-level controls, agent identities and an audit log. It says it is SOC 2 Type II audited.
The catch. A young company in a young category. Ask for the data-flow diagram and the exit plan.
Product
Governs LLM, MCP and agent-to-agent traffic through one gateway, with an AI registry alongside.
The catch. Strongest if you already run Kong for your APIs. Heavy if you don't.
Product, Cloudflare One
Puts several MCP servers behind a single HTTP endpoint in Cloudflare Access, with sign-in, policies and a curated set of tools per portal.
The catch. Part of Cloudflare's zero-trust suite, so it fits best where that suite already sits.
Product, AWS
A managed gateway that turns APIs, Lambda functions and existing services into MCP tools, and routes agent and model traffic through one endpoint.
The catch. Convenient inside AWS. Every tool it creates is another AWS resource to govern.