AI agents call delete_vm 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.
delete_vm removes virtual machines, which is an irreversible destructive action. While the blast radius is somewhat contained (only affects VMs on this host), the action cannot be undone and represents loss of compute infrastructure and any data stored on that VM.
From the tool's definition Tool name 'delete_vm' indicates permanent removal of a virtual machine. No description provided, but the name unambiguously indicates irreversible deletion of infrastructure.
Documented attack patterns abuse exactly the kind of access delete_vm 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_vm:
{
"version": "1",
"default": "deny",
"hide": [
"delete_vm"
]
}delete_vm 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_vm. 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_vm: 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_vm 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 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. 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 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.