upgrade_virtual_machine · CloudStack MCP Server MCP

WHAT IT DOES

What upgrade_virtual_machine does on CloudStack MCP Server

AI agents use upgrade_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 upgrade_virtual_machine needs a policy

Upgrading a virtual machine typically changes its configuration such as CPU, memory, or service offering. This is a reversible modification (can be downgraded), so it falls under Write rather than Destructive. However, it carries high severity because misuse could disrupt running workloads or cause unintended service changes across production infrastructure.

From the tool's definition 'Upgrade virtual machine' - modifies VM configuration (e.g., service offering, hardware specs)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

upgrade_virtual_machine Rate-limited

upgrade_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": {
    "upgrade_virtual_machine": {
      "limits": [
        {
          "counter": "upgrade_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 upgrade_virtual_machine

What does the upgrade_virtual_machine tool do? +

Upgrade virtual machine. 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 upgrade_virtual_machine? +

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

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

Can I rate-limit upgrade_virtual_machine? +

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

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

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