delete_iso

Delete an ISO image.

SERVERVultr MCP SOURCErsp2k/mcp-vultr

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/rsp2k-mcp-vultr/delete-iso.md

WHAT IT DOES

What delete_iso does on Vultr MCP

AI agents call delete_iso to permanently remove resources in Vultr MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_iso is rated Critical

Deletion of ISO images is a destructive operation that cannot be undone. Once deleted, the ISO is permanently removed and cannot be recovered. This falls squarely under Destructive category, with high severity due to potential data loss and infrastructure impact if a critical ISO is removed by mistake.

From the tool's definition Tool name 'delete_iso' explicitly uses 'delete' verb, and description states 'Delete an ISO image' — irreversible removal of cloud infrastructure artifact.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_iso safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Vultr MCP, 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 Hidden

delete_iso 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_iso"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Vultr MCP, apply this rule, and every delete_iso call is checked against it from then on.

FAQ

Questions about delete_iso

What does the delete_iso tool do? +

Delete an ISO image. It is categorised as a Destructive tool in the Vultr MCP 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_iso? +

Register the Vultr 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 Vultr MCP. Nothing to install.

What risk level is delete_iso? +

delete_iso 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_iso? +

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.

How do I block delete_iso completely? +

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.

What MCP server provides delete_iso? +

delete_iso is provided by the Vultr MCP server (rsp2k/mcp-vultr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Vultr, and thousands of servers like it.

This server

All 284 Vultr 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 →