create_container · MCP Developer Server MCP: Risk & Policy

WHAT IT DOES

What create_container does on MCP Developer Server

AI agents invoke create_container to trigger actions in MCP Developer 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

This tool creates and starts a Docker container—an active runtime environment that executes processes. Spawning containers that run indefinitely has a high blast radius: they consume system resources, can run arbitrary workloads, and may expose network services or escape isolation boundaries if misconfigured.

From the tool's definition Create and start a new Docker container that runs indefinitely

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 MCP Developer Server, so you can run agents against it safely.

FAQ

Questions about create_container

What does the create_container tool do? +

Create and start a new Docker container that runs indefinitely. It is categorised as a Execute tool in the MCP Developer 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 MCP Developer 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 MCP Developer 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 MCP Developer Server MCP server (ra86-dev/mcpdev-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.