docker_containers

Manage Docker containers (list, start, stop, remove, etc.)

SERVERCode MCP Server SOURCEagentics-ai/code-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/agentics-ai-code-mcp/docker-containers.md

WHAT IT DOES

What docker_containers does on Code MCP Server

AI agents call docker_containers to permanently remove resources in Code MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why docker_containers is rated Critical

The tool explicitly includes 'remove' among its operations, which irreversibly destroys Docker containers. It also includes start/stop (Execute-level) and list (Read-level), but per the severity hierarchy, the most severe applicable category applies. Removing a container is a destructive, non-reversible action. The blast radius is high since misuse could destroy running production containers or critical services.

From the tool's definition Manage Docker containers (list, start, stop, remove, etc.)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs docker_containers safely

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

docker_containers Hidden

docker_containers is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "docker_containers"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Code MCP Server, apply this rule, and every docker_containers call is checked against it from then on.

FAQ

Questions about docker_containers

What does the docker_containers tool do? +

Manage Docker containers (list, start, stop, remove, etc.). It is categorised as a Destructive tool in the Code MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on docker_containers? +

Register the Code MCP Server MCP server in PolicyLayer and add a rule for docker_containers: 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 Code MCP Server. Nothing to install.

What risk level is docker_containers? +

docker_containers is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit docker_containers? +

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

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

docker_containers is provided by the Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Code MCP Server, and thousands of servers like it.

This server

All 73 Code MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →