start_vm

Start a VM.

SERVERProxmox MCP Server SOURCEgethosthewalrus/proxmox-mcp

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/gethosthewalrus-proxmox-mcp/start-vm.md

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.

RISK

Why start_vm is rated High

Starting a VM is an Execute action because it runs/triggers an external operation with side effects that depend on which VM is specified. It is not Read (retrieves no data), Write (doesn't create/modify VM configuration reversibly), Destructive (doesn't delete data), Financial (no direct monetary impact), or Other.

From the tool's definition Tool description states 'Start a VM' — this triggers an external operation (VM startup) whose effects depend on arguments (which VM to start). Proxmox is infrastructure management, and starting VMs affects running services and resource allocation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs start_vm safely

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

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.

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

FAQ

Questions about start_vm

What does the start_vm tool do? +

Start a VM. 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 (gethosthewalrus/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 286 Proxmox MCP Server tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP →start_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

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