start_virtual_machine · CloudStack MCP Server MCP

WHAT IT DOES

What start_virtual_machine does on CloudStack MCP Server

AI agents invoke start_virtual_machine to trigger actions in CloudStack MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why start_virtual_machine needs a policy

This tool triggers a state change in cloud infrastructure by starting a virtual machine. While not destructive or financial, it executes an operation with real-world infrastructure consequences. Starting a VM can consume resources, trigger cascading processes, and affect dependent services. Misuse could impact availability or incur costs.

From the tool's definition Tool name 'start_virtual_machine' and description 'Start a stopped virtual machine with advanced deployment options' indicate execution of an external operation (VM startup) whose effects depend on which VM is targeted.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_virtual_machine Rate-limited

start_virtual_machine stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_virtual_machine": {
      "limits": [
        {
          "counter": "start_virtual_machine_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 start_virtual_machine

What does the start_virtual_machine tool do? +

Start a stopped virtual machine with advanced deployment options. It is categorised as a Execute tool in the CloudStack MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_virtual_machine? +

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

start_virtual_machine is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_virtual_machine? +

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

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

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