List pods with status, restarts, age, node, and resource usage.
AI agents call k8s_pods to retrieve information from RedisNexus without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries Kubernetes cluster state to return pod metadata and observability data. It performs read-only operations on the cluster, returning information about pod health and resource consumption. There are no side effects, no code execution, and no data modification. The blast radius of misuse is limited to information disclosure about the cluster topology and resource utilization.
From the tool's definition Tool name and description indicate it 'List pods with status, restarts, age, node, and resource usage' — a retrieval operation with no modification, deletion, or execution of workloads.
Attacks that exploit this kind of access
List pods with status, restarts, age, node, and resource usage. It is categorised as a Read tool in the RedisNexus MCP Server, which means it retrieves data without modifying state.
Register the RedisNexus MCP server in PolicyLayer and add a rule for k8s_pods: 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 RedisNexus. Nothing to install.
k8s_pods 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 k8s_pods 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 k8s_pods. 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.
k8s_pods is provided by the RedisNexus MCP server (rajkumar-madhu/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 →