Delete a VM snapshot
AI agents call delete_vm_snapshot 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.
Deleting a snapshot cannot be undone and permanently removes a saved VM state. This is a destructive action that could impact system recovery capabilities and business continuity. While high-severity, it is not critical because it affects a single snapshot rather than the entire VM or cluster. An AI agent misusing this could eliminate important restore points.
From the tool's definition Tool name is 'delete_vm_snapshot' and description states 'Delete a VM snapshot'. The verb 'delete' explicitly indicates irreversible removal of data (a snapshot).
Attacks that exploit this kind of access
Delete a VM snapshot. 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_vm_snapshot: 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_vm_snapshot 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_vm_snapshot 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_vm_snapshot. 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_vm_snapshot is provided by the Proxmox MCP Server MCP server (ry-ops/proxmox-mcp-server). 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 →