migrate_volume

Migrate a volume to another storage pool

SERVERCloudStack MCP Server SOURCEmozg31337/cloudstack-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mozg31337-cloudstack-mcp-server/migrate-volume.md

WHAT IT DOES

What migrate_volume does on CloudStack MCP Server

AI agents use migrate_volume to create or update resources in CloudStack MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CloudStack MCP Server environment.

RISK

Why migrate_volume is rated Medium

Migrating a volume moves it to a different storage pool, which is a Write operation (modifies the storage association/location of the volume). It is not inherently destructive as the data is preserved, but the blast radius is high because migrating the wrong volume or to an incompatible pool could cause data unavailability or VM downtime.

From the tool's definition 'Migrate a volume to another storage pool' — moves data between storage locations

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs migrate_volume 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_volume, this is the rule to start with:

migrate_volume Rate-limited

migrate_volume stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_volume": {
      "limits": [
        {
          "counter": "migrate_volume_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every migrate_volume call is checked against it from then on.

FAQ

Questions about migrate_volume

What does the migrate_volume tool do? +

Migrate a volume to another storage pool. It is categorised as a Write tool in the CloudStack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on migrate_volume? +

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

migrate_volume is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit migrate_volume? +

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

Set action: deny in the PolicyLayer policy for migrate_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_volume? +

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

KEEP EXPLORING

More on CloudStack MCP Server, and thousands of servers like it.

This server

All 442 CloudStack MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →