migrate_vpc · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What migrate_vpc does on CloudStack MCP Server

AI agents invoke migrate_vpc 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_vpc needs a policy

Migrating a VPC to a different zone is a large-scale network infrastructure operation that triggers extensive external changes (reconfiguring routing, subnets, gateways, possibly moving VMs). It is not purely destructive (original may remain or be cleaned up), but it executes a significant orchestrated operation with broad blast radius if misused. Falls under Execute as the most appropriate category.

From the tool's definition 'Migrate VPC to different zone' — migrates an entire VPC infrastructure across zones, triggering complex external operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

migrate_vpc Rate-limited

migrate_vpc 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_vpc": {
      "limits": [
        {
          "counter": "migrate_vpc_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_vpc

What does the migrate_vpc tool do? +

Migrate VPC to different zone. 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_vpc? +

Register the CloudStack MCP Server MCP server in PolicyLayer and add a rule for migrate_vpc: 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_vpc? +

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

Can I rate-limit migrate_vpc? +

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

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

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