create_container · Docker MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_container does on Docker MCP Server

AI agents invoke create_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 create_container needs a policy

Creating and running a Docker container is an Execute-level action: it instantiates a runtime environment that can execute arbitrary processes, expose ports, mount volumes, and interact with the host system. While it also has a Write component (creating container metadata), the dominant risk is the execution of containerized workloads whose effects depend on the image and arguments provided.

From the tool's definition 'Create and run Docker containers with advanced options' — the tool both creates and actively runs containers, triggering external execution environments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_container Rate-limited

create_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": {
    "create_container": {
      "limits": [
        {
          "counter": "create_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 create_container

What does the create_container tool do? +

Create and run Docker containers with advanced options. 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 create_container? +

Register the Docker MCP Server MCP server in PolicyLayer and add a rule for create_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 create_container? +

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

Can I rate-limit create_container? +

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

Set action: deny in the PolicyLayer policy for create_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 create_container? +

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