destroy_virtual_machine

THE RISK

Critical Risk

Why destroy_virtual_machine needs a policy

This tool permanently removes a virtual machine and its associated resources through a multi-stage destruction workflow (stop, destroy, expunge). The operation cannot be reversed. In a CloudStack environment, destroying a VM is a high-impact action affecting infrastructure, compute resources, and potentially dependent services. An AI agent misusing this tool could cause significant operational damage.

From the tool's definition Tool name 'destroy_virtual_machine' combined with description stating 'Destroy a virtual machine using proper workflow: stop → destroy → expunge' and explicit marker '(DESTRUCTIVE - cannot be undone)' indicates irreversible deletion of infrastructure.

Documented attack patterns abuse exactly the kind of access destroy_virtual_machine gives an agent:

POLICY

How to control destroy_virtual_machine

PolicyLayer is an MCP gateway — it sits between your AI agents and CloudStack MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for destroy_virtual_machine:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "destroy_virtual_machine"
  ]
}

destroy_virtual_machine disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register CloudStack MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More CloudStack MCP Server tools

Execute deploy_virtual_machine Deploy a new virtual machine Execute scale_virtual_machine Scale virtual machine (change service offering) Execute start_virtual_machine Start a virtual machine Execute stop_virtual_machine Stop a virtual machine Execute reboot_virtual_machine Reboot a virtual machine Execute migrate_virtual_machine Migrate virtual machine to another host Write reset_password_virtual_machine Reset password for virtual machine Write associate_ip_address Acquire a new public IP address

All 45 CloudStack MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in CloudStack MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about destroy_virtual_machine

What does the destroy_virtual_machine tool do? +

Destroy a virtual machine using proper workflow: stop → destroy → expunge. Handles VMs in any state including Error. (DESTRUCTIVE - cannot be undone). It is categorised as a Destructive tool in the CloudStack MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on destroy_virtual_machine? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for destroy_virtual_machine: 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 CloudStack MCP Server. Nothing to install.

What risk level is destroy_virtual_machine? +

destroy_virtual_machine is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit destroy_virtual_machine? +

Yes. Add a rate_limit block to the destroy_virtual_machine 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.

How do I block destroy_virtual_machine completely? +

Set action: deny in the PolicyLayer policy for destroy_virtual_machine. 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.

What MCP server provides destroy_virtual_machine? +

destroy_virtual_machine is provided by the CloudStack MCP Server MCP server (phantosmax/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CloudStack MCP Server tool call.

Start from CloudStack MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →