rename_vm · Mcp Utm MCP: Risk & Policy

WHAT IT DOES

What rename_vm does on Mcp Utm

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

Renaming a VM is a non-destructive modification that alters only the name attribute of an existing resource. While it changes state, the operation is easily reversible (can be renamed again) and does not delete, execute code, or commit financial obligations. It falls clearly into the Write category.

From the tool's definition Tool performs 'Rename a stopped VM' — a metadata modification operation that changes the name of a virtual machine resource. This is a reversible write operation with no data deletion or destructive effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_vm Rate-limited

rename_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": {
    "rename_vm": {
      "limits": [
        {
          "counter": "rename_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 rename_vm

What does the rename_vm tool do? +

Rename a stopped VM. 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 rename_vm? +

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

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

Can I rate-limit rename_vm? +

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

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

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