This record as markdown: /tools/aapanel-mcp/docker-image-delete.md
What docker_image_delete does on Aapanel
AI agents call docker_image_delete to permanently remove resources in Aapanel, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why docker_image_delete is rated Critical
Deleting a Docker image cannot be undone and permanently removes the artifact from the registry/local storage. This is a destructive operation with high blast radius: an AI agent could delete critical production images, disrupt deployments, or cause service outages. While not directly financial, the impact severity justifies 'Destructive' classification and 'high' severity rating.
From the tool's definition Tool name explicitly uses 'delete' verb and description states 'Delete a Docker image' — this removes a Docker image irreversibly from the system.
Attacks that exploit this kind of access
The rule that runs docker_image_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aapanel, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For docker_image_delete, this is the rule to start with:
docker_image_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aapanel, apply this rule, and every docker_image_delete call is checked against it from then on.
Questions about docker_image_delete
Delete a Docker image. It is categorised as a Destructive tool in the Aapanel MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aapanel MCP server in PolicyLayer and add a rule for docker_image_delete: 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 Aapanel. Nothing to install.
docker_image_delete 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 docker_image_delete 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 docker_image_delete. 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.
docker_image_delete is provided by the Aapanel MCP server (nipunanirmal/aapanel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aapanel, and thousands of servers like it.
Across the catalogue