get_next_vmid

What get_next_vmid does on Proxmox MCP Server

AI agents call get_next_vmid to retrieve information from Proxmox MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_next_vmid is rated Low

The tool retrieves information (the next available VM ID) from the Proxmox cluster. No side effects occur—it does not create, modify, delete, or execute any actions. This is a pure read operation similar to listing or fetching data. Severity is low because misuse poses minimal risk; an AI agent learning what the next available VMID is cannot cause harm on its own.

From the tool's definition Tool name is 'get_next_vmid' and description states 'Get the next available VMID in the cluster' — this is a query/retrieval operation that returns data without modifying any infrastructure state or triggering external operations.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_next_vmid": {}
  }
}

Questions about get_next_vmid