bulk_migrate_guests
Bulk migrate guests to a target node.
This record as markdown: /tools/gethosthewalrus-proxmox-mcp/bulk-migrate-guests.md
What bulk_migrate_guests does on Proxmox MCP Server
AI agents invoke bulk_migrate_guests 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.
Why bulk_migrate_guests is rated High
Migrating guests (VMs/containers) in bulk triggers live infrastructure operations — moving workloads between nodes — which are external, potentially disruptive operations. While not strictly irreversible (guests can be migrated back), the act of bulk migration can cause service interruptions, network reconfiguration, and resource contention across the cluster, making it a high-severity Execute action.
From the tool's definition Bulk migrate guests to a target node
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs bulk_migrate_guests 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 bulk_migrate_guests, this is the rule to start with:
bulk_migrate_guests 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Proxmox MCP Server, apply this rule, and every bulk_migrate_guests call is checked against it from then on.
Questions about bulk_migrate_guests
Bulk migrate guests to a target node. 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.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for bulk_migrate_guests: 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.
bulk_migrate_guests is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the bulk_migrate_guests 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.
Set action: deny in the PolicyLayer policy for bulk_migrate_guests. 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.
bulk_migrate_guests 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.
More on Proxmox MCP Server, and thousands of servers like it.
Across the catalogue