pve_api_request · Proxmox MCP: Risk & Policy

WHAT IT DOES

What pve_api_request does on Proxmox

AI agents invoke pve_api_request to trigger actions in Proxmox. 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 IT NEEDS A POLICY

Why pve_api_request needs a policy

This tool can invoke arbitrary Proxmox API endpoints including POST, PUT, and DELETE operations (with confirm=true). This means it can execute any operation supported by the Proxmox API—including destructive actions like deleting VMs, modifying configurations, or triggering migrations—making it an unrestricted execution surface.

From the tool's definition Call any Proxmox API path. GET is allowed; POST/PUT/DELETE require confirm=true.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pve_api_request Rate-limited

pve_api_request 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": {
    "pve_api_request": {
      "limits": [
        {
          "counter": "pve_api_request_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Proxmox, so you can run agents against it safely.

FAQ

Questions about pve_api_request

What does the pve_api_request tool do? +

Call any Proxmox API path. GET is allowed; POST/PUT/DELETE require confirm=true. It is categorised as a Execute tool in the Proxmox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pve_api_request? +

Register the Proxmox MCP server in PolicyLayer and add a rule for pve_api_request: 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. Nothing to install.

What risk level is pve_api_request? +

pve_api_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit pve_api_request? +

Yes. Add a rate_limit block to the pve_api_request 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 pve_api_request completely? +

Set action: deny in the PolicyLayer policy for pve_api_request. 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 pve_api_request? +

pve_api_request is provided by the Proxmox MCP server (plgonzalezrx8/proxmox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.