docker_container_action

Run a safe Docker container action: start, stop, restart, pause, unpause, or kill.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/docker-container-action.md

WHAT IT DOES

What docker_container_action does on Mcp Control Plane

AI agents invoke docker_container_action to trigger actions in Mcp Control Plane. 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.

RISK

Why docker_container_action is rated High

This tool executes commands that control running container state and can interrupt services, cause downtime, or trigger cascading failures in dependent systems. While labeled 'safe' (suggesting filtering), the blast radius of misuse is significant—an agent could kill production containers.

From the tool's definition Tool directly runs Docker container lifecycle actions (start, stop, restart, pause, unpause, kill) that trigger external operations on running containers. Description explicitly states 'Run a...action' with named operations that execute against infrastructure.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs docker_container_action safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_container_action, this is the rule to start with:

docker_container_action Rate-limited

docker_container_action 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": {
    "docker_container_action": {
      "limits": [
        {
          "counter": "docker_container_action_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every docker_container_action call is checked against it from then on.

FAQ

Questions about docker_container_action

What does the docker_container_action tool do? +

Run a safe Docker container action: start, stop, restart, pause, unpause, or kill. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on docker_container_action? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for docker_container_action: 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 Control Plane. Nothing to install.

What risk level is docker_container_action? +

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

Can I rate-limit docker_container_action? +

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

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

docker_container_action is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools → High-risk tools on this server →

Across the catalogue

qt_trigger_action on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →