pve_stop_vm · Proxmox MCP Server MCP: Risk & Policy

WHAT IT DOES

What pve_stop_vm does on Proxmox MCP Server

AI agents invoke pve_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 pve_stop_vm needs a policy

Stopping a VM is an Execute action: it runs a command that triggers external state changes in the Proxmox infrastructure. While graceful shutdown is reversible (VM can be restarted), it has significant blast radius in production environments—an agent that stops the wrong VM could disrupt services, running workloads, and dependent systems.

From the tool's definition pve_stop_vm - Stop a VM (graceful shutdown). This tool triggers an external operation (VM shutdown) whose effects depend on the target VM argument.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pve_stop_vm Rate-limited

pve_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": {
    "pve_stop_vm": {
      "limits": [
        {
          "counter": "pve_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 pve_stop_vm

What does the pve_stop_vm tool do? +

Stop a VM (graceful 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 pve_stop_vm? +

Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for pve_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 pve_stop_vm? +

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

Can I rate-limit pve_stop_vm? +

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

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

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