start_virtual_machine

THE RISK

High Risk

Why start_virtual_machine needs a policy

This tool triggers execution of a command against CloudStack infrastructure to start a virtual machine. While not destructive (the VM isn't deleted or permanently modified) and not financial, it is a definitive Execute action—it performs an external operation whose consequences are determined by the arguments provided (which VM to start).

From the tool's definition Tool name 'start_virtual_machine' and description 'Start a virtual machine' indicate execution of an operation that triggers external infrastructure state changes.

Documented attack patterns abuse exactly the kind of access start_virtual_machine gives an agent:

POLICY

How to control start_virtual_machine

PolicyLayer is an MCP gateway — it sits between your AI agents and CloudStack MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for start_virtual_machine:

policy.json

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

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.

Create a free account and register CloudStack MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More CloudStack MCP Server tools

Destructive destroy_virtual_machine Destroy a virtual machine using proper workflow: stop → destroy → expunge. Handles VMs in Execute deploy_virtual_machine Deploy a new virtual machine Execute scale_virtual_machine Scale virtual machine (change service offering) Execute stop_virtual_machine Stop a virtual machine Execute reboot_virtual_machine Reboot a virtual machine Execute migrate_virtual_machine Migrate virtual machine to another host Write reset_password_virtual_machine Reset password for virtual machine Write associate_ip_address Acquire a new public IP address

All 45 CloudStack MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in CloudStack MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about start_virtual_machine

What does the start_virtual_machine tool do? +

Start a virtual machine. 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 (phantosmax/cloudstack-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every CloudStack MCP Server tool call.

Start from CloudStack MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →