migrate_vm_with_volume · CloudStack MCP Server MCP

WHAT IT DOES

What migrate_vm_with_volume does on CloudStack MCP Server

AI agents invoke migrate_vm_with_volume 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 IT NEEDS A POLICY

Why migrate_vm_with_volume needs a policy

VM migration with volumes is an Execute-class operation: it moves a live virtual machine and its attached storage across hosts/pools. While not inherently destructive (data is not deleted), it is a high-impact infrastructure operation that can cause downtime, affect multiple dependent systems, and if misused (e.g., migrating to an incompatible host) can crash workloads.

From the tool's definition 'Migrate virtual machine with volumes' - migrates a running VM and its storage to different infrastructure

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

migrate_vm_with_volume Rate-limited

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CloudStack MCP Server, so you can run agents against it safely.

FAQ

Questions about migrate_vm_with_volume

What does the migrate_vm_with_volume tool do? +

Migrate virtual machine with volumes. 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.

How do I enforce a policy on migrate_vm_with_volume? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for migrate_vm_with_volume: 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.

What risk level is migrate_vm_with_volume? +

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

Can I rate-limit migrate_vm_with_volume? +

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

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

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