vm_delete
Delete a virtual machine. This is a DESTRUCTIVE operation. The
This record as markdown: /tools/spranab-truenas-mcp/vm-delete.md
What vm_delete does on Truenas
AI agents call vm_delete to permanently remove resources in Truenas, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why vm_delete is rated Critical
Deleting a virtual machine permanently removes a compute resource and all associated state. This operation cannot be undone and represents a complete loss of the VM and its data. The tool explicitly self-identifies as DESTRUCTIVE, making this the most severe category. The blast radius is critical: an agent misusing this tool could delete production VMs, causing service outages and data loss.
From the tool's definition Tool name 'vm_delete' combined with explicit description stating 'This is a DESTRUCTIVE operation.' The description itself uses the word DESTRUCTIVE in all caps to emphasize the irreversible nature of the action.
Attacks that exploit this kind of access
The rule that runs vm_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Truenas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vm_delete, this is the rule to start with:
vm_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 Truenas, apply this rule, and every vm_delete call is checked against it from then on.
Questions about vm_delete
Delete a virtual machine. This is a DESTRUCTIVE operation. The. It is categorised as a Destructive tool in the Truenas MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Truenas MCP server in PolicyLayer and add a rule for vm_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 Truenas. Nothing to install.
vm_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_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_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_delete is provided by the Truenas MCP server (spranab/truenas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Truenas, and thousands of servers like it.
Across the catalogue