Delete a container (stops and removes it)
AI agents call delete_container to permanently remove resources in MCP Developer Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of Docker containers is an irreversible destructive action that cannot be undone. While the blast radius is limited to a single container rather than permanent data loss, it still destroys running environments and any state within them. This is more severe than Write (reversible modifications) or Execute (code with predictable bounded effects), placing it in the Destructive category.
From the tool's definition Tool name explicitly states 'delete_container' and description confirms it 'stops and removes it' — irreversible removal of infrastructure/data.
Attacks that exploit this kind of access
Delete a container (stops and removes it). It is categorised as a Destructive tool in the MCP Developer Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Developer 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 MCP Developer 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 MCP Developer Server MCP server (ra86-dev/mcpdockershell). 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 →