Get Proxmox cluster status and health
AI agents call pve_get_cluster_status to retrieve information from Proxmox MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries cluster health metrics and status without modifying, executing, or deleting any resources. It has no side effects and poses minimal risk even if called by an agent—the worst outcome is information disclosure about infrastructure status, which has low blast radius.
From the tool's definition Tool name and description indicate retrieval of cluster status and health information: 'Get Proxmox cluster status and health'. The verb 'Get' and lack of modification language ('create', 'delete', 'update') confirm read-only data retrieval.
Attacks that exploit this kind of access
Get Proxmox cluster status and health. It is categorised as a Read tool in the Proxmox MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Proxmox MCP Server MCP server in PolicyLayer and add a rule for pve_get_cluster_status: 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 MCP Server. Nothing to install.
pve_get_cluster_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the pve_get_cluster_status 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.
Set action: deny in the PolicyLayer policy for pve_get_cluster_status. 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.
pve_get_cluster_status is provided by the Proxmox MCP Server MCP server (mjrestivo16/mcp-proxmox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →