destroy_system_vm

Destroy system virtual machine

SERVERCloudStack MCP Server SOURCEmozg31337/cloudstack-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mozg31337-cloudstack-mcp-server/destroy-system-vm.md

WHAT IT DOES

What destroy_system_vm does on CloudStack MCP Server

AI agents call destroy_system_vm to permanently remove resources in CloudStack MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why destroy_system_vm is rated Critical

This tool permanently deletes a system virtual machine, which is an irreversible operation that cannot be undone. System VMs are critical infrastructure components in CloudStack. Misuse by an AI agent could result in loss of essential services and data. The destruction of system infrastructure components represents the most severe category of risk.

From the tool's definition Tool name explicitly includes 'destroy' and description states 'Destroy system virtual machine'. The term 'destroy' indicates irreversible deletion of infrastructure.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs destroy_system_vm safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For destroy_system_vm, this is the rule to start with:

destroy_system_vm Hidden

destroy_system_vm is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every destroy_system_vm call is checked against it from then on.

FAQ

Questions about destroy_system_vm

What does the destroy_system_vm tool do? +

Destroy system virtual machine. 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_system_vm? +

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

What risk level is destroy_system_vm? +

destroy_system_vm 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_system_vm? +

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

How do I block destroy_system_vm completely? +

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

What MCP server provides destroy_system_vm? +

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

KEEP EXPLORING

More on CloudStack MCP Server, and thousands of servers like it.

This server

All 442 CloudStack MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →