proxmox_delete_lxc
A destructive tool on the MCP Proxmox MCP server.
This record as markdown: /tools/bsahane-mcp-proxmox/proxmox-delete-lxc.md
What proxmox_delete_lxc does on MCP Proxmox Server
AI agents call proxmox_delete_lxc to permanently remove resources in MCP Proxmox Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why proxmox_delete_lxc is rated Critical
Proxmox_delete_lxc performs irreversible deletion of LXC (Linux Container) instances. This is a destructive operation—once executed, the container and its data are permanently removed and cannot be undone. The blast radius is critical because an AI agent with access to this tool could destroy entire containerized workloads and their persistent data without recovery options.
From the tool's definition Tool name 'proxmox_delete_lxc' explicitly indicates deletion of LXC containers in Proxmox infrastructure. The server description confirms this tool operates on Proxmox virtualization infrastructure supporting 'VM/LXC lifecycle operations.' Deletion of…
Attacks that exploit this kind of access
The rule that runs proxmox_delete_lxc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Proxmox Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For proxmox_delete_lxc, this is the rule to start with:
proxmox_delete_lxc 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 MCP Proxmox Server, apply this rule, and every proxmox_delete_lxc call is checked against it from then on.
Questions about proxmox_delete_lxc
proxmox_delete_lxc is a destructive tool on the MCP Proxmox Server MCP server. It is categorised as a Destructive tool in the MCP Proxmox Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Proxmox Server MCP server in PolicyLayer and add a rule for proxmox_delete_lxc: 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 Proxmox Server. Nothing to install.
proxmox_delete_lxc 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 proxmox_delete_lxc 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 proxmox_delete_lxc. 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.
proxmox_delete_lxc is provided by the MCP Proxmox Server MCP server (bsahane/mcp-proxmox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Proxmox Server, and thousands of servers like it.
Across the catalogue