detach_iso · Hcloud MCP: Risk & Policy

WHAT IT DOES

What detach_iso does on Hcloud

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

WHY IT NEEDS A POLICY

Why detach_iso needs a policy

Detaching an ISO modifies the server's configuration by removing an attached ISO image. This is a reversible action (the ISO can be re-attached), so it falls under Write rather than Destructive. Misuse could disrupt a server that relies on the ISO for booting or installation, hence medium severity.

From the tool's definition Detach an ISO from a server

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

detach_iso Rate-limited

detach_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": {
    "detach_iso": {
      "limits": [
        {
          "counter": "detach_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 Hcloud, so you can run agents against it safely.

FAQ

Questions about detach_iso

What does the detach_iso tool do? +

Detach an ISO from a server. It is categorised as a Write tool in the Hcloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on detach_iso? +

Register the Hcloud MCP server in PolicyLayer and add a rule for detach_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 Hcloud. Nothing to install.

What risk level is detach_iso? +

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

Can I rate-limit detach_iso? +

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

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

detach_iso is provided by the Hcloud MCP server (xodus-co/hcloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.