delete_container
A destructive tool on the Proxmox MCP server.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/delete-container.md
What delete_container does on Proxmox MCP Server
AI agents call delete_container to permanently remove resources in Proxmox MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_container is rated Critical
The delete operation on infrastructure resources is irreversible and destructive. While the description is empty (lowering confidence slightly from critical to high), the explicit 'delete' verb applied to a container—a running or persistent compute unit in Proxmox—clearly indicates data/resource destruction that cannot be undone.
From the tool's definition Tool name is 'delete_container' with empty description. The verb 'delete' combined with 'container' (a Proxmox compute resource) indicates irreversible removal of infrastructure.
Attacks that exploit this kind of access
The rule that runs delete_container safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_container, this is the rule to start with:
delete_container 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 Proxmox MCP Server, apply this rule, and every delete_container call is checked against it from then on.
Questions about delete_container
delete_container is a destructive tool on the Proxmox MCP Server MCP server. It is categorised as a Destructive tool in the Proxmox MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Proxmox 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 Proxmox 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 Proxmox MCP Server MCP server (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Proxmox MCP Server, and thousands of servers like it.
Across the catalogue