docker_container_stop · Docker MCP: Risk & Policy

WHAT IT DOES

What docker_container_stop does on Docker MCP

AI agents invoke docker_container_stop to trigger actions in Docker MCP. 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.

WHY IT NEEDS A POLICY

Why docker_container_stop needs a policy

Stopping a container is an Execute action—it triggers an external operation with side effects that persist beyond the function call. While reversible (the container can be restarted), it disrupts running services and workloads. This is not Read (no data retrieval), not Write (not creating/modifying persistent data), not Destructive (the container and data remain; it is not deleted), and not Financial.

From the tool's definition Tool name: docker_container_stop. Description: 'Stop a running container'. This performs an external operation (halting a container process) whose effects depend on which container is specified as an argument.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

docker_container_stop Rate-limited

docker_container_stop stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "docker_container_stop": {
      "limits": [
        {
          "counter": "docker_container_stop_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Docker MCP, so you can run agents against it safely.

FAQ

Questions about docker_container_stop

What does the docker_container_stop tool do? +

Stop a running container. It is categorised as a Execute tool in the Docker MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on docker_container_stop? +

Register the Docker MCP server in PolicyLayer and add a rule for docker_container_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. Nothing to install.

What risk level is docker_container_stop? +

docker_container_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit docker_container_stop? +

Yes. Add a rate_limit block to the docker_container_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.

How do I block docker_container_stop completely? +

Set action: deny in the PolicyLayer policy for docker_container_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.

What MCP server provides docker_container_stop? +

docker_container_stop is provided by the Docker MCP server (sondt2709/docker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.