bulk_start_guests

What bulk_start_guests does on Proxmox MCP Server

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

This tool executes infrastructure operations (starting multiple VMs/containers) whose effects depend on which guests are specified as arguments. While not destructive or financial, it materially changes system state and could disrupt services, consume resources, or trigger cascading effects if misused at scale (hence 'bulk' operation).

From the tool's definition Tool name is 'bulk_start_guests' and description states it 'Bulk start guests across the cluster.' Starting virtual machines/containers is an operational action that triggers execution of compute resources and affects infrastructure state.

Risk signalsBulk/mass operation — affects multiple targets

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

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

Questions about bulk_start_guests