startall_node

What startall_node does on Proxmox MCP Server

AI agents invoke startall_node 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 startall_node is rated High

This tool executes a command that initiates multiple guest systems. While not destructive or financial, it is an Execute-category operation because it triggers external infrastructure operations with side effects that cannot be rolled back simply by re-running the tool. The severity is high because unintended activation of all VMs on a node could disrupt services, consume resources, and affect system availability.

From the tool's definition Tool description states it 'Start all VMs and containers on a node' — this is an action that triggers external operations (starting multiple virtual machines and containers) whose effects depend on which node is targeted.

The rule that runs startall_node 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 startall_node, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "startall_node": {
      "limits": [
        {
          "counter": "startall_node_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about startall_node