migrate_vm

A execute tool on the Proxmox MCP server.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gethosthewalrus-proxmox-mcp/migrate-vm.md

WHAT IT DOES

What migrate_vm does on Proxmox MCP Server

AI agents invoke migrate_vm to trigger actions in Proxmox MCP Server. 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.

RISK

Why migrate_vm is rated High

Migrating a VM moves it between nodes/hosts, which is an operational action that triggers external infrastructure changes. It is not purely destructive (data is preserved) but it executes a significant infrastructure operation.

From the tool's definition Tool name 'migrate_vm' on a Proxmox VE management server; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs migrate_vm safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Proxmox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For migrate_vm, this is the rule to start with:

migrate_vm Rate-limited

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": {
    "migrate_vm": {
      "limits": [
        {
          "counter": "migrate_vm_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every migrate_vm call is checked against it from then on.

FAQ

Questions about migrate_vm

What does the migrate_vm tool do? +

migrate_vm is a execute tool on the Proxmox MCP Server MCP server. It is categorised as a Execute tool in the Proxmox MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on migrate_vm? +

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

What risk level is migrate_vm? +

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

Can I rate-limit migrate_vm? +

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

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

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

KEEP EXPLORING

More on Proxmox MCP Server, and thousands of servers like it.

This server

All 286 Proxmox MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →