Stop Docker containers
AI agents invoke docker-stop to trigger actions in Docker MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
While stopping a container is technically reversible (containers can be restarted), the tool executes external Docker operations whose effects depend on which container(s) are targeted.
From the tool's definition Tool name 'docker-stop' with description 'Stop Docker containers' indicates execution of container lifecycle operations. This performs irreversible state transitions of running containers, affecting system resources and application availability.
Attacks that exploit this kind of access
Stop Docker containers. It is categorised as a Execute tool in the Docker MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Docker MCP Server MCP server in PolicyLayer and add a rule for docker-stop: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Docker MCP Server. Nothing to install.
docker-stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the docker-stop rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for docker-stop. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
docker-stop is provided by the Docker MCP Server MCP server (0xshariq/docker-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
docker-stop is one line of Docker MCP Server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →