Skip to content
MoorAI
03 — agents & architecture

MCP gateway

A proxy between agents and MCP servers that tool listings and tool calls pass through, so one place can authenticate, allow or refuse servers and tools, inspect arguments and results, and log. It sees only the MCP traffic routed through it: a server an agent connects to directly, and actions that are not MCP calls, such as shell commands and file reads, are outside it.

How MoorAI handles it: moorai-mcp-gateway sits in front of remote MCP servers and evaluates every tools/call; a stdio proxy does the same for local servers.

See also MCP · tool poisoning · model proxy

Sources

Related terms

  • MCP Agents & architecture

    An open protocol, introduced by Anthropic in 2024 and now broadly adopted, that standardises how agents connect to external tools and data sources.

  • Tool poisoning Attack concepts

    Hiding instructions in the metadata an agent reads to learn how to use a tool — an MCP server's tool description, its parameter documentation, its schema…

  • Model proxy Agents & architecture

    A service between an application or agent and its model provider's API: the client points its base URL at the proxy, which forwards each request and can…

Agents & architecture

Where the attacks above actually land. The vocabulary here is worth precision, because the difference between "the model decided" and "the tool ran" is the difference between a risk and an incident.

MCP gateway is term 12 of 16 in this part of the glossary.

Get started free Full glossary → How we test → Community agent on GitHub ↗

This page is one entry from the agentic AI security glossary, which defines 82 terms in the same style. Where a term belongs to a published taxonomy or standard — the HackAgent attack families, the OWASP lists, AMTSO's guidelines, MITRE ATLAS, ISO/IEC 42001, the NIST AI RMF, the EU AI Act, W3C Trace Context, the MCP specification — the authoritative wording is the source document's, not ours, and specifics should be verified there. "Lethal trifecta" is Simon Willison's term. OWASP® is a trademark of the OWASP Foundation; ATT&CK® and ATLAS™ are trademarks of The MITRE Corporation. Naming a framework here is description, not a claim of certification or endorsement.