attach_drive · Mcp Utm MCP: Risk & Policy

WHAT IT DOES

What attach_drive does on Mcp Utm

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

WHY IT NEEDS A POLICY

Why attach_drive needs a policy

Attaching a drive is a write operation that modifies VM configuration but does not execute arbitrary code, delete data, or cause irreversible damage. The action is reversible (drive can be detached). While it could indirectly enable malicious activities (e.g., booting from a malicious ISO), the tool itself performs a configuration modification rather than executing those operations.

From the tool's definition Tool description states 'Attach an ISO or disk image to a removable drive' - this modifies VM configuration by adding/mounting a drive attachment, which is a reversible change to VM state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

attach_drive Rate-limited

attach_drive 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": {
    "attach_drive": {
      "limits": [
        {
          "counter": "attach_drive_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 Mcp Utm, so you can run agents against it safely.

FAQ

Questions about attach_drive

What does the attach_drive tool do? +

Attach an ISO or disk image to a removable drive. It is categorised as a Write tool in the Mcp Utm MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on attach_drive? +

Register the Mcp Utm MCP server in PolicyLayer and add a rule for attach_drive: 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 Mcp Utm. Nothing to install.

What risk level is attach_drive? +

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

Can I rate-limit attach_drive? +

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

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

attach_drive is provided by the Mcp Utm MCP server (neverprepared/mcp-utm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.