Show resource usage for nodes
AI agents call top-nodes to retrieve information from Kubernetes 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 and displays resource usage metrics (CPU, memory, etc.) for Kubernetes nodes. It is a read-only operation with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an attacker could only gain visibility into cluster resource utilization, which does not compromise system integrity or enable further attacks directly.
From the tool's definition Tool name 'top-nodes' and description 'Show resource usage for nodes' indicate a query/display operation that retrieves monitoring data without modifying, executing operations, or deleting resources.
Attacks that exploit this kind of access
Show resource usage for nodes. It is categorised as a Read tool in the Kubernetes MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes MCP Server MCP server in PolicyLayer and add a rule for top-nodes: 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 Kubernetes MCP Server. Nothing to install.
top-nodes 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 top-nodes 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 top-nodes. 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.
top-nodes is provided by the Kubernetes MCP Server MCP server (thekaranpargaie/kube-mcp). 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 →