// MCP TOOL REFERENCE

stop_container

Stop a running Docker container

Halts running workloads

Part of the Docker MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@ckreiling/mcp-server-docker Execute Risk 4/5

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke stop_container to trigger processes or run actions in Docker. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON STOP_CONTAINER

stop_container can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

docker.yaml

tools:
  stop_container:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Docker policy for all 19 tools.

// DETAILS

Tool Name stop_container

Category Execute

MCP Server Docker MCP Server

Risk Level High

// MORE DOCKER TOOLS

Destructive remove_container Destructive remove_image Destructive remove_network Destructive remove_volume Execute build_image Execute recreate_container Execute run_container Execute start_container

View all 19 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like stop_container have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Agent Passport System — Cryptographic Identity for AI Agents commerce_preflight Agent Passport System — Cryptographic Identity for AI Agents execute_with_context Agent Passport System — Cryptographic Identity for AI Agents gateway_execute_approval Agent Passport System — Cryptographic Identity for AI Agents governance_360 Agent Passport System — Cryptographic Identity for AI Agents parse_governance_block_html AgentClear — API Marketplace for AI Agents call_service

// IN CONTEXT OF HIGH RISK

stop_container is one of the high-risk operations in Docker. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the stop_container tool do? +

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

How do I enforce a policy on stop_container? +

Add a rule in your Intercept YAML policy under the tools section for stop_container. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Docker MCP server.

What risk level is stop_container? +

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

Can I rate-limit stop_container? +

Yes. Add a rate_limit block to the stop_container rule in your Intercept 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 stop_container completely? +

Set action: deny in the Intercept policy for stop_container. 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 stop_container? +

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

stop_container

Enforce policies on Docker