High Risk →

run_container

Launch a Docker container

Runs arbitrary code in containers

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

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

AI agents invoke run_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.

run_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.

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

docker.yaml
tools:
  run_container:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Docker policy for all 19 tools.

Tool Name run_container
Category Execute
MCP Server Docker MCP Server
Risk Level High

View all 19 tools →

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

Browse the full MCP Attack Database →

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

run_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.

What does the run_container tool do? +

Launch a 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 run_container? +

Add a rule in your Intercept YAML policy under the tools section for run_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 run_container? +

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

Can I rate-limit run_container? +

Yes. Add a rate_limit block to the run_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 run_container completely? +

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

run_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.

Enforce policies on Docker

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.