pause_container · Docker MCP Server MCP: Risk & Policy

WHAT IT DOES

What pause_container does on Docker MCP Server

AI agents invoke pause_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 pause_container needs a policy

Pausing a container suspends all processes within it, which is an operational state change that affects running workloads. This is an external operation that triggers an effect on a running container. It is reversible (containers can be unpaused), so it doesn't qualify as Destructive, but it is more than a simple Write since it executes a control operation on a running system.

From the tool's definition Pause all processes within a container

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pause_container Rate-limited

pause_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": {
    "pause_container": {
      "limits": [
        {
          "counter": "pause_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 pause_container

What does the pause_container tool do? +

Pause all processes within a container. 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 pause_container? +

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

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

Can I rate-limit pause_container? +

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

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

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