Elimina un contenedor Docker por nombre
AI agents call delete_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.
Deleting a Docker container is an irreversible operation that removes the container and its state. This cannot be undone without recreation, making it a destructive action with potentially significant blast radius if triggered on the wrong container (data loss, service interruption). It exceeds Execute severity due to its permanent nature.
From the tool's definition Tool name 'delete_container' and description 'Elimina un contenedor Docker por nombre' (Delete a Docker container by name) indicate irreversible deletion of container resources.
Attacks that exploit this kind of access
Elimina un contenedor Docker por nombre. 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 delete_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.
delete_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 delete_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 delete_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.
delete_container is provided by the Docker MCP Server MCP server (rodrigouc/docker-mcp). 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 →