bulk_migrate_guests

Bulk migrate guests to a target node.

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/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

Questions about bulk_migrate_guests

What does the bulk_migrate_guests tool do? +

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.

How do I enforce a policy on bulk_migrate_guests? +

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.

What risk level is bulk_migrate_guests? +

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

Can I rate-limit bulk_migrate_guests? +

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.

How do I block bulk_migrate_guests completely? +

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.

What MCP server provides bulk_migrate_guests? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Proxmox MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.