AI agents call delete_snapshot to permanently remove resources in Virtualization — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Snapshot deletion is an irreversible operation. While not as critical as deleting an entire VM, removing snapshots eliminates restore points and cannot be undone. This qualifies as Destructive rather than Execute. The confidence is high based on the explicit 'delete' verb in the tool name, despite the empty description.
From the tool's definition Tool name is 'delete_snapshot' which indicates deletion of VM snapshots. Server context shows lifecycle management of virtual machines. Snapshots are point-in-time states that, once deleted, cannot be recovered.
Documented attack patterns abuse exactly the kind of access delete_snapshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Virtualization, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_snapshot:
{
"version": "1",
"default": "deny",
"hide": [
"delete_snapshot"
]
}delete_snapshot disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
delete_snapshot. It is categorised as a Destructive tool in the Virtualization MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Virtualization MCP server in PolicyLayer and add a rule for delete_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 Virtualization. Nothing to install.
delete_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_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_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_snapshot is provided by the Virtualization MCP server (sandraschi/virtualization-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Virtualization, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
56 Virtualization tools catalogued and risk-classified — across an index of 43,000+ MCP servers.