Remove VMware datacenter
AI agents call remove_vmware_dc 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.
This tool irreversibly deletes a VMware datacenter, which is a critical infrastructure component. Deletion of a datacenter cannot be reversed and results in loss of all associated resources, configurations, and potentially running services. This qualifies as a Destructive operation with high severity due to the large blast radius (all VMs, storage, and networking in that datacenter would be affected).
From the tool's definition Tool name 'remove_vmware_dc' combined with description 'Remove VMware datacenter' indicates deletion of infrastructure resources.
Attacks that exploit this kind of access
Remove VMware datacenter. 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 remove_vmware_dc: 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.
remove_vmware_dc 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 remove_vmware_dc 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 remove_vmware_dc. 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.
remove_vmware_dc 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 →