delete_host

Delete hypervisor host

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/delete-host.md

WHAT IT DOES

What delete_host does on CloudStack MCP Server

AI agents call delete_host 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 delete_host is rated Critical

Deleting a hypervisor host from CloudStack infrastructure is a destructive operation that permanently removes compute capacity, affecting all virtual machines and services dependent on that host. This is categorized as Destructive rather than Execute because the operation is inherently irreversible and constitutes a permanent change to infrastructure state.

From the tool's definition Tool name 'delete_host' explicitly performs deletion; description states 'Delete hypervisor host'. Deletion of infrastructure components is irreversible and cannot be undone.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_host 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 delete_host, this is the rule to start with:

delete_host Hidden

delete_host 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": [
    "delete_host"
  ]
}

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 delete_host call is checked against it from then on.

FAQ

Questions about delete_host

What does the delete_host tool do? +

Delete hypervisor host. 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 delete_host? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for delete_host: 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 delete_host? +

delete_host 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 delete_host? +

Yes. Add a rate_limit block to the delete_host 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 delete_host completely? +

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

delete_host 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

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →