Skip to content

Category 5 of 12 · Controls: The tool-call chokepoint

MCP and AI gateways

Gateways and proxies that sit between agents and the tools they call, enforcing authentication, allow lists, and inspection on Model Context Protocol and model traffic.

Mitigates: ASI02 Tool Misuse and Exploitation, ASI04 Agentic Supply Chain Vulnerabilities, ASI07 Insecure Inter-Agent Communication, LLM06 Excessive Agency · MITRE ATLAS AML.T0053

Vendors, by signal score

Ranked within this category only. How the score works.

Also covers this category

Questions to ask a vendor

  1. Does the gateway implement MCP OAuth conformance and block token passthrough?
  2. Can it allow list servers and individual tools per agent?
  3. Does it log every tool call with the identity chain?

Go deeper

FAQ

Why put a gateway in front of MCP servers?
Every MCP server is a new way for an agent to act. A gateway gives one place to authenticate, restrict which tools each agent may call, and record what happened.
What is token passthrough and why is it banned?
Forwarding the client's token straight to a downstream API. The MCP authorization spec forbids it because the downstream service cannot tell the token was meant for someone else.