The safeguards map / 3.3 Gateways

Docker MCP Gateway

Docker (company). No foundation, not yet generally available. MIT. Listed; 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

An open-source Docker CLI plugin that runs Model Context Protocol (MCP) servers in containers behind one gateway, with secret blocking and per-tool enable and disable.

Where it sits

3.3 Gateways (primary): Sits between MCP clients and the MCP servers it runs in containers, blocks secrets passing to and from tools and lets the operator disable individual tools.

AI models access MCP servers through a single Gateway.

captured

Block secrets from being/received sent to/from tools

captured

disable one or more tools

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

None recorded.

Listed, not drawn: it is not yet generally available, and no documented handoff and no foundation home places it on the map.

Collector's note

Every release in the repository's list carries the publisher's Pre-release label, so maturity is pre-ga. The run command also accepts interceptors, external programs run before or after a call; no policy language is documented.

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.