update_virtual_machine · CloudStack MCP Server MCP

WHAT IT DOES

What update_virtual_machine does on CloudStack MCP Server

AI agents use update_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 update_virtual_machine needs a policy

This tool creates or modifies virtual machine configuration reversibly (e.g., CPU, memory, tags, settings). While modifications to running infrastructure carry significant blast radius if misapplied, they are typically reversible through subsequent updates. Classified as Write rather than Execute because it modifies state directly rather than triggering code execution.

From the tool's definition Tool name 'update_virtual_machine' and description 'Update virtual machine properties' indicate modification of existing infrastructure state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_virtual_machine Rate-limited

update_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": {
    "update_virtual_machine": {
      "limits": [
        {
          "counter": "update_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 update_virtual_machine

What does the update_virtual_machine tool do? +

Update virtual machine properties. 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 update_virtual_machine? +

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

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

Can I rate-limit update_virtual_machine? +

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

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

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