run_container · Docker MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_container does on Docker MCP Server

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

WHY IT NEEDS A POLICY

Why run_container needs a policy

This tool does not merely read data (Read), nor does it only create reversible metadata structures (Write). Running a container initiates actual code execution in an isolated environment. While generally safer than executing arbitrary shell commands on the host, a container can still perform destructive or malicious operations depending on its image, mounted volumes, and environment variables.

From the tool's definition Tool description states 'Run a container (create and start)' which executes containerized code/processes. The server description confirms it 'enables AI assistants to manage Docker containers' with 'container lifecycle management' capabilities.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_container Rate-limited

run_container 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": {
    "run_container": {
      "limits": [
        {
          "counter": "run_container_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 Server, so you can run agents against it safely.

FAQ

Questions about run_container

What does the run_container tool do? +

Run a container (create and start). This is the preferred method for starting 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.

How do I enforce a policy on run_container? +

Register the Docker MCP Server MCP server in PolicyLayer and add a rule for run_container: 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.

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 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 run_container completely? +

Set action: deny in the PolicyLayer 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 MCP server (swartdraak/docker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.