The safeguards map / 3.3 Gateways
Runlayer
Drafted with AI
Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made
A commercial Model Context Protocol (MCP) gateway with access rules evaluated by its proxy on every tool call, argument conditions, built-in scanners and custom scanners that call an operator's endpoint.
Where it sits
3.3 Gateways (primary): Sits on the request path between agents and MCP servers, and allows or denies each tool call from the owner's access rules, argument conditions and an optional operator-hosted scanner endpoint.
Connect AI to your tools through one gateway
captured
server-level allow/deny rules and global deny rules, evaluated by the proxy on every tool invocation
captured
Add runtime rules based on tool arguments (e.g., restrict SQL queries to specific tables)
captured
Send MCP traffic to your own scanning service and enforce its allow/deny verdict
captured
Facts
- Concern
- security
- Names the law
- no
- Subject
- agentAI system
- Used by
- those who run it
- Runs
- at runtime
- Policy comes from
- owner-entered settingsan external decision point
- Traffic it sees
- tool calls (MCP)
- Can the agent bypass it
- depends
Handoffs
None recorded.
Listed, not drawn: no documented handoff and no foundation home places it on the map.
Every quote is verbatim from a stored capture of the page linked under it. Placement is our reading of the product's own documentation; no publisher has reviewed or endorsed it. Rows CC BY 4.0. Names, marks and logos belong to their owners; logos identify each product and are not part of the dataset.