Stop and remove a container, then run a new container. Fails if the container does not exist.
AI agents call recreate_container to permanently remove resources in Docker MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Removing a container is an irreversible action that destroys the container's state and configuration. Although the tool also creates a new container afterward, the removal step cannot be undone without external backups. This falls squarely into Destructive (irreversibly deletes data/resources) rather than Execute (which would apply to commands whose effects depend on arguments but are generally reversible).
From the tool's definition Tool description explicitly states 'Stop and remove a container' — removal is an irreversible deletion action. The tool combines stopping (reversible) with removal (destructive), making destruction the defining operation.
Attacks that exploit this kind of access
Stop and remove a container, then run a new container. Fails if the container does not exist. It is categorised as a Destructive tool in the Docker MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Docker MCP Server MCP server in PolicyLayer and add a rule for recreate_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.
recreate_container is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the recreate_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.
Set action: deny in the PolicyLayer policy for recreate_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.
recreate_container is provided by the Docker MCP Server MCP server (pnmice/mcp-server-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →