Delete a Virtual Private Cloud
AI agents call delete_vpc 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.
Deleting a VPC is a destructive operation that cannot be undone and will remove the entire virtual network along with associated resources. This is more severe than Write (reversible modifications) or Execute (code execution with variable outcomes). The server mentions a 'safety confirmation system for destructive operations', which further confirms this tool belongs in the Destructive category.
From the tool's definition Tool name is 'delete_vpc' and description states 'Delete a Virtual Private Cloud'. The verb 'delete' combined with a critical infrastructure resource (VPC) indicates irreversible data removal.
Attacks that exploit this kind of access
Delete a Virtual Private Cloud. 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 delete_vpc: 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.
delete_vpc 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_vpc 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_vpc. 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_vpc 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.
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 →