update_iso · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_iso does on CloudStack MCP Server

AI agents use update_iso to create or update resources in CloudStack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.

WHY IT NEEDS A POLICY

Why update_iso needs a policy

This is a Write operation—it modifies existing ISO metadata/properties without deleting or destroying data. While it affects infrastructure, the reversible nature (properties can be updated again) and the fact that it doesn't execute code or cause irreversible changes places it in Write rather than Execute or Destructive.

From the tool's definition Tool name is 'update_iso' and description states 'Update ISO properties'. ISO files are image files used to boot virtual machines; updating their properties modifies existing data reversibly without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_iso Rate-limited

update_iso stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_iso": {
      "limits": [
        {
          "counter": "update_iso_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CloudStack MCP Server, so you can run agents against it safely.

FAQ

Questions about update_iso

What does the update_iso tool do? +

Update ISO properties. It is categorised as a Write tool in the CloudStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_iso? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_iso? +

update_iso is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_iso? +

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

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

update_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.