19 tools. 14 can modify or destroy data without limits.
4 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (remove_container, remove_image, remove_network) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (create_container, create_network, create_volume) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (build_image, recreate_container, run_container) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Docker. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @ckreiling/mcp-server-docker remove_container:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
create_container:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
fetch_container_logs:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Docker server exposes 4 destructive tools including remove_container, remove_image, remove_network. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Docker server has 5 write tools including create_container, create_network, create_volume. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
19 tools across 4 categories: Destructive, Execute, Read, Write. 5 are read-only. 14 can modify, create, or delete data.
One line change. Instead of running the Docker server directly, prefix it with Intercept: intercept -c docker.yaml -- npx -y @@ckreiling/mcp-server-docker. Download a pre-built policy from policylayer.com/policies/docker and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init