Get status and resource usage for a specific node
AI agents call get_node_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 and returns node status and resource metrics (CPU, memory, disk, etc.) from Proxmox. It has no side effects, does not modify infrastructure, does not execute commands, and does not delete or create resources. It is a straightforward read/retrieval operation consistent with similar tools on the same server (get_cluster_status, get_container_status, get_storage_status, get_vm_status).
From the tool's definition Tool name 'get_node_status' and description 'Get status and resource usage for a specific node' indicate a read-only query operation that retrieves current state information without modifying or executing anything.
Attacks that exploit this kind of access
Get status and resource usage for a specific node. 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 get_node_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.
get_node_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 get_node_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 get_node_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.
get_node_status is provided by the Proxmox MCP Server MCP server (ry-ops/proxmox-mcp-server). 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 →