Destroy ALL Docker resources for a LaunchFrame project (containers, volumes, images, network). IRREVERSIBLE — all local data including database volumes will be lost. Will prompt for confirmation before proceeding.
AI agents call cli_docker_destroy to permanently remove resources in LaunchFrame MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly destroys multiple categories of resources (containers, volumes, images, networks) and explicitly warns that local data and database volumes will be lost with no recovery option. This is a destructive action that cannot be undone, fitting the Destructive category. Severity is critical due to the total data loss potential and broad blast radius across an entire Docker environment for a project.
From the tool's definition Tool description explicitly states 'Destroy ALL Docker resources' and 'IRREVERSIBLE — all local data including database volumes will be lost.' The name 'cli_docker_destroy' and description make clear this irreversibly deletes/removes data and resources that…
Attacks that exploit this kind of access
Destroy ALL Docker resources for a LaunchFrame project (containers, volumes, images, network). IRREVERSIBLE — all local data including database volumes will be lost. Will prompt for confirmation before proceeding. It is categorised as a Destructive tool in the LaunchFrame MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LaunchFrame MCP server in PolicyLayer and add a rule for cli_docker_destroy: 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 LaunchFrame MCP. Nothing to install.
cli_docker_destroy 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 cli_docker_destroy 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 cli_docker_destroy. 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.
cli_docker_destroy is provided by the LaunchFrame MCP server (launchframe-dev/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 →