start_vm · Proxmox MCP Server MCP: Risk & Policy

WHAT IT DOES

What start_vm does on Proxmox MCP Server

AI agents invoke start_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 start_vm needs a policy

This tool executes an action that changes system state (bringing a VM online) but is not destructive, financial, or a write operation in the data sense. It directly triggers external operations on virtualization infrastructure. While reversible (a VM can be stopped), the execution of infrastructure commands and the blast radius of an AI agent unintentionally starting critical VMs places this in the Execute category.

From the tool's definition Tool performs 'Start a virtual machine' - a command that triggers execution of infrastructure state changes. Starting a VM is an operational action that executes system-level operations with real infrastructure consequences.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_vm Rate-limited

start_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": {
    "start_vm": {
      "limits": [
        {
          "counter": "start_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 start_vm

What does the start_vm tool do? +

Start a virtual machine. 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 start_vm? +

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

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

Can I rate-limit start_vm? +

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

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

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