proxmox_wait_task

What proxmox_wait_task does on MCP Proxmox Server

AI agents invoke proxmox_wait_task to trigger actions in MCP Proxmox 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 proxmox_wait_task is rated High

While 'wait_task' itself does not directly modify state, in Proxmox context it synchronously monitors and waits for infrastructure operations initiated by other tools. It triggers external effects tied to running tasks (VM power states, snapshot creation, backup execution). The potential for misuse exists if an agent maliciously waits for destructive tasks or fails to properly handle task completion logic.

From the tool's definition Tool name 'proxmox_wait_task' indicates blocking/waiting on a Proxmox task operation. The server description states it 'Enables comprehensive management of Proxmox virtualization infrastructure' with 'VM/LXC lifecycle operations' and 'Provides full access to…

The rule that runs proxmox_wait_task safely

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

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

Questions about proxmox_wait_task