New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_vmware_dc

Remove VMware datacenter

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/remove-vmware-dc.md

What remove_vmware_dc does on CloudStack MCP Server

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.

Why remove_vmware_dc is rated Critical

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.

Questions about remove_vmware_dc

What does the remove_vmware_dc tool do? +

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.

How do I enforce a policy on remove_vmware_dc? +

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.

What risk level is remove_vmware_dc? +

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.

Can I rate-limit remove_vmware_dc? +

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.

How do I block remove_vmware_dc completely? +

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.

What MCP server provides remove_vmware_dc? +

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.

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of CloudStack MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.