proxmox_api_gateway

What proxmox_api_gateway does on MCP Proxmox Server

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

This tool deploys an API gateway, which is an infrastructure operation that executes and triggers external effects (network reconfiguration, service provisioning). While not immediately destructive or financial, it modifies the production Proxmox environment and its effects depend on deployment arguments. This fits Execute category as it runs an operation whose consequences depend on how it is invoked.

From the tool's definition 'Deploy API gateway for enhanced API management' indicates launching/provisioning infrastructure that triggers external operations and modifies the Proxmox environment. API gateway deployment is an operational action that executes infrastructure changes.

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

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

Questions about proxmox_api_gateway