The safeguards map / 3.3 Gateways
Azure API Management AI gateway
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
The AI gateway features of Azure API Management: governance of model, Model Context Protocol (MCP) server and Agent2Agent (A2A) agent API traffic, including content safety checks on prompts and tool traffic.
Where it sits
3.3 Gateways (primary): Sits in front of language model APIs, remote MCP servers and A2A agent APIs and applies API Management policies, including content safety checks that block a request or response.
Govern chat completions, responses, and real-time APIs.
captured
Remote MCP servers and A2A agent APIs
captured
The policy can also enforce content safety checks on requests or responses for MCP tools or A2A Agent APIs managed in API Management.
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 settings
- Traffic it sees
- model callstool calls (MCP)agent to agent (A2A)
- 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.