stop_system_vm

Stop a system virtual machine

SERVERCloudStack MCP Server SOURCEmozg31337/cloudstack-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mozg31337-cloudstack-mcp-server/stop-system-vm.md

WHAT IT DOES

What stop_system_vm does on CloudStack MCP Server

AI agents invoke stop_system_vm 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.

RISK

Why stop_system_vm is rated High

Stopping a system VM is an Execute action—it triggers an external operation (halting a running virtual machine) whose effects depend on arguments and operational context. While not permanently destructive (the VM can be restarted), it causes immediate service disruption.

From the tool's definition Tool name 'stop_system_vm' and description 'Stop a system virtual machine' indicate execution of a control operation on critical infrastructure. System VMs are essential components in CloudStack that provide core services.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_system_vm safely

PolicyLayer is an MCP gateway: it sits between your AI agents and CloudStack MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stop_system_vm, this is the rule to start with:

stop_system_vm Rate-limited

stop_system_vm 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_system_vm": {
      "limits": [
        {
          "counter": "stop_system_vm_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect CloudStack MCP Server, apply this rule, and every stop_system_vm call is checked against it from then on.

FAQ

Questions about stop_system_vm

What does the stop_system_vm tool do? +

Stop a system 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_system_vm? +

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

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

Can I rate-limit stop_system_vm? +

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

Set action: deny in the PolicyLayer policy for stop_system_vm. 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_system_vm? +

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

KEEP EXPLORING

More on CloudStack MCP Server, and thousands of servers like it.

This server

All 442 CloudStack MCP Server tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →