assign_virtual_machine · CloudStack MCP Server MCP

WHAT IT DOES

What assign_virtual_machine does on CloudStack MCP Server

AI agents use assign_virtual_machine 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_virtual_machine needs a policy

Assigning a virtual machine to a different account is a write operation that modifies resource metadata and ownership, with potential security implications if misused (e.g., transferring resources to unauthorized accounts). It is reversible, so not Destructive.

From the tool's definition Tool name is 'assign_virtual_machine' with description 'Assign virtual machine to account'. Assignment operations modify resource ownership/account associations, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

assign_virtual_machine Rate-limited

assign_virtual_machine 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_virtual_machine": {
      "limits": [
        {
          "counter": "assign_virtual_machine_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_virtual_machine

What does the assign_virtual_machine tool do? +

Assign virtual machine to 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_virtual_machine? +

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

What risk level is assign_virtual_machine? +

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

Can I rate-limit assign_virtual_machine? +

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

How do I block assign_virtual_machine completely? +

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

What MCP server provides assign_virtual_machine? +

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