Route every MCP connection. Govern every call. Log everything that happens. Block what shouldn't get through.
Metorial Gateway
Every MCP connection through one governed path
When agents connect to tools through many different routes, no one can govern or see the whole picture. The Metorial Gateway fixes that by routing every MCP connection through a single path, whether it's a Magic MCP server, a custom server, a remote server, or a Docker-based one. One place becomes the point of control, visibility, and protection.
- 01
Route everything through one place.
All MCP connections pass through the gateway. There's a single, consistent path for every agent-to-tool interaction.
- 02
Govern and record every call.
Because all traffic flows through the gateway, every tool call, message, and execution can be controlled by policy and logged for review.
- 03
Protect traffic as it flows.
The gateway applies firewall rules and monitors for attacks. Routing everything through one path also makes traffic easier to keep secure.
Governance and logging
Every call governed and on the record
Because all MCP traffic flows through the gateway, it's the natural place to apply policy and capture a complete record of what happened.
Policy
Govern every call
Every tool call is checked against policies and access control. An agent can only do what it's allowed to.
Logging
A complete record
Calls, messages, and executions are recorded in audit logs. Nothing happens off the record.
Visibility
See it as it runs
Traffic feeds observability and monitors and alerts. You can watch behavior and act on it in real time.
Security and protection
Inspected and defended on the way through
The single path is also the single place to enforce network rules and screen traffic for attacks before it reaches a tool.
Firewalls
Control the traffic
Firewalls enforce ingress and egress rules on traffic through the gateway. Each connection only reaches what it should.
Protoguard
Screen for exploits
Protoguard, Metorial's prompt security system, inspects traffic for prompt injection and other exploits before it reaches a tool.
Containment
Stop the bad ones
Malicious or misbehaving traffic can be blocked at the gateway. A single bad actor can't spread.
Recent updates to Metorial GatewayView all
What the gateway covers
Central by design
- MCP connections routed through itAll
- Calls logged and monitoredAll of them
- Connection types unifiedMagic, custom, remote, Docker
- Firewall and attack monitoringBuilt in
FAQ
Answers to common questions about metorial gateway and how they fit into governed AI agent infrastructure.
What is the Metorial Gateway?
It's a central gateway that all MCP traffic in your organization passes through. Every MCP connection routes through it, which makes it the single place to govern, log, and protect agent-to-tool traffic.What kinds of connections go through the gateway?
All of them, including Magic MCP servers, custom MCP servers, remote MCP servers, and Docker MCP servers.What does routing through one gateway give me?
A single point of control and visibility. Every tool call, message, and execution can be governed by policy and logged, with nothing bypassing your controls.Does the gateway protect against attacks?
Yes. The gateway applies firewall rules and uses prompt injection monitoring to watch MCP traffic for attacks and malicious activity.Is gateway traffic logged?
Yes. Every call through the gateway is logged and monitored for security and compliance, and is available in audit logs.How does the gateway relate to providers?
Providers are the connections themselves. The gateway is the path their traffic flows through, applying governance and protection consistently across all of them.