stop_virtual_machine · CloudStack MCP Server MCP

WHAT IT DOES

What stop_virtual_machine does on CloudStack MCP Server

AI agents invoke stop_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 stop_virtual_machine needs a policy

Stopping a virtual machine is an execute action that triggers an external operation with real infrastructure consequences. While not permanently destructive (the VM can be restarted), it represents a significant operational impact that interrupts services and availability. This falls under Execute rather than Destructive because the action is reversible—the VM can be started again.

From the tool's definition Tool name 'stop_virtual_machine' and description 'Stop a running virtual machine' indicate execution of an operation that halts a running system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_virtual_machine Rate-limited

stop_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": {
    "stop_virtual_machine": {
      "limits": [
        {
          "counter": "stop_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 stop_virtual_machine

What does the stop_virtual_machine tool do? +

Stop a running 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 stop_virtual_machine? +

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

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

Can I rate-limit stop_virtual_machine? +

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

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

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