This record as markdown: /tools/mozg31337-cloudstack-mcp-server/delete-iso.md
What delete_iso does on CloudStack MCP Server
AI agents call delete_iso 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 delete_iso is rated Critical
This tool irreversibly deletes ISO artifacts from the CloudStack infrastructure. Deletion is a one-way operation that cannot be undone. While the server description mentions a 'safety confirmation system for destructive operations' which may provide some mitigation, the underlying action is still destructive in nature.
From the tool's definition Tool name is 'delete_iso' and description states 'Delete an ISO'. ISO images are infrastructure artifacts that cannot be recovered once deleted without external backups.
Attacks that exploit this kind of access
The rule that runs delete_iso 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_iso, this is the rule to start with:
delete_iso 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 delete_iso call is checked against it from then on.
Questions about delete_iso
Delete an ISO. 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_iso: 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_iso 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_iso 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_iso. 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_iso 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