Delete a VM permanently. Cannot be undone.
AI agents call delete_vm to permanently remove resources in Mcp Utm — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes virtual machine instances, which qualifies as a Destructive action per the classification rules. While the blast radius depends on the importance of the deleted VM, the permanent and unrecoverable nature of the operation, combined with potential loss of data and configurations within the VM, warrants a 'high' severity rating.
From the tool's definition Tool description explicitly states 'Delete a VM permanently. Cannot be undone.' The name 'delete_vm' combined with the irreversible nature of permanently deleting a virtual machine clearly indicates destructive capability.
Attacks that exploit this kind of access
Delete a VM permanently. Cannot be undone. It is categorised as a Destructive tool in the Mcp Utm MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Utm 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 Mcp Utm. 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 Mcp Utm MCP server (neverprepared/mcp-utm). 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 →