Get resource usage metrics for a pod
AI agents call get_pod_metrics 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 resource usage information (CPU, memory, etc.) about an existing pod. 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 gather operational intelligence about pod performance but cannot affect cluster state or resources.
From the tool's definition Tool name 'get_pod_metrics' and description 'Get resource usage metrics for a pod' indicate data retrieval only. The verb 'get' and 'metrics' confirm querying existing data without modification or execution.
Attacks that exploit this kind of access
Get resource usage metrics for a pod. 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 get_pod_metrics: 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.
get_pod_metrics 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_pod_metrics 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_pod_metrics. 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_pod_metrics is provided by the Kubernetes MCP Server MCP server (surukanti/k8s-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 →