vm_device_delete
Delete a VM device by its ID. Optionally delete the associated zvol or raw file.
This record as markdown: /tools/nasbridge/vm-device-delete.md
What vm_device_delete does on Nasbridge
AI agents call vm_device_delete to permanently remove resources in Nasbridge, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why vm_device_delete is rated Critical
This tool permanently removes VM devices and associated storage volumes without recovery. VM devices and zvolumes cannot be recovered once deleted, making this a destructive action with critical blast radius. An AI agent instructed to clean up or optimize could irreversibly destroy production virtual infrastructure and data.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete a VM device by its ID' with capability to 'delete the associated zvol or raw file', which are irreversible storage operations.
Attacks that exploit this kind of access
The rule that runs vm_device_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vm_device_delete, this is the rule to start with:
vm_device_delete 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 Nasbridge, apply this rule, and every vm_device_delete call is checked against it from then on.
Questions about vm_device_delete
Delete a VM device by its ID. Optionally delete the associated zvol or raw file. It is categorised as a Destructive tool in the Nasbridge MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Nasbridge MCP server in PolicyLayer and add a rule for vm_device_delete: 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 Nasbridge. Nothing to install.
vm_device_delete 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 vm_device_delete 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 vm_device_delete. 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.
vm_device_delete is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
Across the catalogue