pve_migrate_vm · Proxmox MCP: Risk & Policy

WHAT IT DOES

What pve_migrate_vm does on Proxmox

AI agents invoke pve_migrate_vm to trigger actions in Proxmox. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why pve_migrate_vm needs a policy

Migrating a VM/container to another node is an external infrastructure operation that moves a running or stopped workload across nodes. It is not purely destructive (data is not deleted), not financial, but it triggers a significant external operation with real side effects (network reconfiguration, resource reallocation, potential downtime). This fits Execute.

From the tool's definition Migrate a VM/container to another node. Requires confirm=true.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pve_migrate_vm Rate-limited

pve_migrate_vm stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pve_migrate_vm": {
      "limits": [
        {
          "counter": "pve_migrate_vm_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about pve_migrate_vm

What does the pve_migrate_vm tool do? +

Migrate a VM/container to another node. Requires confirm=true. It is categorised as a Execute tool in the Proxmox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pve_migrate_vm? +

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

What risk level is pve_migrate_vm? +

pve_migrate_vm is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pve_migrate_vm? +

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

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

pve_migrate_vm is provided by the Proxmox MCP server (plgonzalezrx8/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.