stop_vm · Proxmox MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_vm does on Proxmox MCP Server

AI agents invoke stop_vm to trigger actions in Proxmox 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_vm needs a policy

This tool executes a command against infrastructure (forced VM shutdown) rather than merely reading data (Read), reversibly modifying data (Write), or permanently destroying it (Destructive). While the VM remains intact post-shutdown, the forced nature and operational impact on running services make this Execute-category.

From the tool's definition Tool performs 'forced shutdown' of a virtual machine, which is an external operation that triggers immediate state change with effects dependent on which VM is specified as an argument.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_vm Rate-limited

stop_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_vm": {
      "limits": [
        {
          "counter": "stop_vm_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 Proxmox MCP Server, so you can run agents against it safely.

FAQ

Questions about stop_vm

What does the stop_vm tool do? +

Stop a virtual machine (forced shutdown). It is categorised as a Execute tool in the Proxmox 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_vm? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for stop_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 Proxmox MCP Server. Nothing to install.

What risk level is stop_vm? +

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

Can I rate-limit stop_vm? +

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

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

stop_vm is provided by the Proxmox MCP Server MCP server (ry-ops/proxmox-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

stop_vm is one line of Proxmox MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →