Agent tool / platformFree source toolLiveFrom public docs
Docker MCP Gateway
Docker
The Docker CLI plugin behind MCP Toolkit: containerized MCP servers with tool allowlists.
Overview
Docker MCP Gateway powers the MCP Toolkit in Docker Desktop and also runs standalone. Local MCP servers run in isolated containers, credentials go through Docker Desktop secrets management, profiles allowlist individual tools, and built-in logging traces each call.
Production criteria
| Approval gatesCan a person or policy hold an action until it is approved? | Not claimed Not documented by the vendor or not yet reviewed. |
|---|---|
| Restart recoveryDoes work resume after a crash or redeploy without repeating finished steps? | Not claimed Not documented by the vendor or not yet reviewed. |
| Evidence trailCan you inspect what ran, with what inputs, and who approved it? | Built in Built-in logging and call tracing. |
| Kill switchCan an operator withdraw permission or stop further actions? | Not claimed Not documented by the vendor or not yet reviewed. |
| Policy controlsDo declared rules decide which tools and actions are allowed? | Documented pattern Per-profile allowlists enable or disable individual tools. |
| Sandbox isolationDoes code or tool execution run inside an isolated boundary? | Built in Local MCP servers run in isolated containers with minimal host privileges. |
Marks reflect the documentation linked below as of 2026-10-29. How we mark criteria.
Limits and scope
- Some Docker governance features are edition-specific; check what your plan includes.
Also in MCP gateways & tool policy
- ToolHive — Run and manage MCP servers in isolated containers, with access policy and audit logs.
- agentgateway — Open-source proxy for agent and tool traffic over MCP and A2A, with CEL policy.
Free tools, a product pilot, or a focused paid diagnosis.
Choose a tool from the directory, explore Mothership’s technical pilot path, or check fit for a software diagnosis when one issue needs investigation.