migrate_virtual_machine
Migrate a virtual machine to another host
This record as markdown: /tools/mozg31337-cloudstack-mcp-server/migrate-virtual-machine.md
What migrate_virtual_machine does on CloudStack MCP Server
AI agents invoke migrate_virtual_machine to trigger actions in CloudStack 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_virtual_machine is rated High
Migrating a VM is an Execute-class operation: it triggers an external infrastructure operation (live or cold migration) that moves workloads between hosts. It is not destructive (the VM and its data are preserved), but it carries high severity because misuse (wrong target host, wrong VM) can cause service disruption, resource contention, or downtime in a production environment.
From the tool's definition 'Migrate a virtual machine to another host' — moves a running VM across hosts, triggering live or cold migration with significant infrastructure impact
Attacks that exploit this kind of access
The rule that runs migrate_virtual_machine safely
PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For migrate_virtual_machine, this is the rule to start with:
migrate_virtual_machine 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 CloudStack MCP Server, apply this rule, and every migrate_virtual_machine call is checked against it from then on.
Questions about migrate_virtual_machine
Migrate a virtual machine to another host. It is categorised as a Execute tool in the CloudStack MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for migrate_virtual_machine: 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 CloudStack MCP Server. Nothing to install.
migrate_virtual_machine 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 migrate_virtual_machine 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 migrate_virtual_machine. 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.
migrate_virtual_machine is provided by the CloudStack MCP Server MCP server (mozg31337/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CloudStack MCP Server, and thousands of servers like it.
Across the catalogue