Get CPU, memory, and storage usage for a node
AI agents call pve_get_node_resources 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 retrieves resource utilization metrics (CPU, memory, storage) from a Proxmox node. It is purely informational with no side effects, reversible actions, code execution, data deletion, or financial impact. It falls squarely into the Read category with low severity since exposure would only allow monitoring data access, not control or modification of infrastructure.
From the tool's definition Tool name 'pve_get_node_resources' and description 'Get CPU, memory, and storage usage for a node' indicate a query/retrieval operation that returns monitoring data without modifying or executing anything.
Attacks that exploit this kind of access
Get CPU, memory, and storage usage for a 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 pve_get_node_resources: 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_node_resources 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_node_resources 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_node_resources. 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_node_resources 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 →