reboot_virtual_machine · CloudStack MCP Server MCP

WHAT IT DOES

What reboot_virtual_machine does on CloudStack MCP Server

AI agents invoke reboot_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 reboot_virtual_machine needs a policy

Rebooting a virtual machine is an external operation that disrupts running workloads and services. It is not purely destructive (data is not deleted) but it executes an action with significant operational impact. Misuse could cause service outages for any workloads running on the VM, warranting a high severity rating.

From the tool's definition 'Reboot a virtual machine' — triggers an external operation (restart) on a running VM

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reboot_virtual_machine Rate-limited

reboot_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": {
    "reboot_virtual_machine": {
      "limits": [
        {
          "counter": "reboot_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 reboot_virtual_machine

What does the reboot_virtual_machine tool do? +

Reboot 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 reboot_virtual_machine? +

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

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

Can I rate-limit reboot_virtual_machine? +

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

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

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