migrate_container

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-container.md

What migrate_container does on Proxmox MCP Server

AI agents invoke migrate_container 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 migrate_container is rated High

Migration of a container in Proxmox VE involves moving a running or stopped container from one node to another, which is an operational action with significant infrastructure impact. It is analogous to sibling tools like 'bulk_migrate_guests', suggesting it triggers external infrastructure operations.

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

Questions about migrate_container

What does the migrate_container tool do? +

migrate_container 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_container? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for migrate_container: 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_container? +

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

Can I rate-limit migrate_container? +

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

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

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