expunge_virtual_machine
Permanently delete a virtual machine
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/expunge-virtual-machine.md
What expunge_virtual_machine does on CloudStack MCP Server
AI agents call expunge_virtual_machine 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.
Why expunge_virtual_machine is rated Critical
This tool performs a permanent, irreversible deletion of a virtual machine—a core infrastructure asset. Expunge operations cannot be undone, and accidental or malicious use could result in complete loss of compute resources, data, and service availability.
From the tool's definition Tool name 'expunge_virtual_machine' combined with description 'Permanently delete a virtual machine' explicitly indicates irreversible deletion of infrastructure resources.
Attacks that exploit this kind of access
The rule that runs expunge_virtual_machine 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 expunge_virtual_machine, this is the rule to start with:
expunge_virtual_machine 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 CloudStack MCP Server, apply this rule, and every expunge_virtual_machine call is checked against it from then on.
Questions about expunge_virtual_machine
Permanently delete a 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.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for expunge_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.
expunge_virtual_machine 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 expunge_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.
Set action: deny in the PolicyLayer policy for expunge_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.
expunge_virtual_machine 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.
More on CloudStack MCP Server, and thousands of servers like it.
Across the catalogue