clone_vm · Mcp Utm MCP: Risk & Policy

WHAT IT DOES

What clone_vm does on Mcp Utm

AI agents use clone_vm 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 clone_vm needs a policy

Cloning a VM creates a new virtual machine instance, which is a reversible write operation. It does not delete or overwrite existing data, execute arbitrary code, or involve financial transactions. The new VM can be deleted if needed, making this a Write category action. Medium severity because spawning VMs consumes system resources and could be misused at scale.

From the tool's definition Clone a UTM template VM with a unique random MAC address

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

clone_vm Rate-limited

clone_vm 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": {
    "clone_vm": {
      "limits": [
        {
          "counter": "clone_vm_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 clone_vm

What does the clone_vm tool do? +

Clone a UTM template VM with a unique random MAC address. 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 clone_vm? +

Register the Mcp Utm MCP server in PolicyLayer and add a rule for clone_vm: 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 clone_vm? +

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

Can I rate-limit clone_vm? +

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

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

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