assign_volume · CloudStack MCP Server MCP: Risk & Policy

WHAT IT DOES

What assign_volume does on CloudStack MCP Server

AI agents use assign_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.

WHY IT NEEDS A POLICY

Why assign_volume needs a policy

Assigning a volume changes metadata and ownership but does not destroy data or execute arbitrary code. However, the severity is elevated (high rather than medium) because reassigning storage volumes could impact availability and access control for other accounts, and an unauthorized reassignment could expose sensitive data or deny legitimate users access to their storage.

From the tool's definition Tool description states 'Assign volume to different account', which modifies the ownership/association of a storage volume. The action is reversible—a volume can be reassigned to another account. This is a data modification operation without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

assign_volume Rate-limited

assign_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": {
    "assign_volume": {
      "limits": [
        {
          "counter": "assign_volume_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 assign_volume

What does the assign_volume tool do? +

Assign volume to different account. 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 assign_volume? +

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

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

Can I rate-limit assign_volume? +

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

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

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