Destroy a Vagrant VM (force)
AI agents call destroy_vm to permanently remove resources in Virtualbox MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a VM and cannot be undone. The 'force' flag indicates forceful termination without graceful shutdown. If an AI agent misuses this tool, it could irreversibly delete production VMs, development environments, or critical infrastructure. This has the highest severity impact as the action cannot be reversed.
From the tool's definition Tool name is 'destroy_vm' and description states 'Destroy a Vagrant VM (force)'. The word 'destroy' combined with 'force' indicates irreversible deletion of the virtual machine and all associated data.
Attacks that exploit this kind of access
Destroy a Vagrant VM (force). It is categorised as a Destructive tool in the Virtualbox MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Virtualbox MCP Server MCP server in PolicyLayer and add a rule for destroy_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 Virtualbox MCP Server. Nothing to install.
destroy_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 destroy_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 destroy_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.
destroy_vm is provided by the Virtualbox MCP Server MCP server (usemanusai/virtualbox-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 →