The safeguards map / 3.3 Gateways

Zuplo MCP Gateway

Zuplo (company). Vendor, generally available. proprietary. Mapped; as of .

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 Zuplo gateway that fronts remote Model Context Protocol (MCP) servers behind one OAuth-protected endpoint, curates the tools each route exposes and exports traces and logs in OTLP.

Where it sits

3.3 Gateways (primary): Sits between MCP clients and upstream MCP servers, authenticating users, limiting which tools each route exposes and composing with Zuplo guardrail policies.

For each MCP request, the gateway authenticates the user against your identity provider, mints an independent upstream credential

captured

Curate which tools each route exposes.

captured

Compose the gateway with Zuplo's PII redaction, prompt injection detection, and other security policies.

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
tool calls (MCP)
Can the agent bypass it
depends

Handoffs

produces Runtime records: OTLP traces and logs

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.