Get all pods managed by a ReplicaSet
AI agents call get_replicaset_pods 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 information about pods associated with a ReplicaSet. It is a read-only query operation that does not create, modify, delete, or execute code. The action is informational only, making it a Read category tool with low severity since exposure would only allow an AI agent to view existing pod information without the ability to alter infrastructure state.
From the tool's definition Tool name 'get_replicaset_pods' and description 'Get all pods managed by a ReplicaSet' indicate a retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
Get all pods managed by a ReplicaSet. 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_replicaset_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 Kubernetes MCP Server. Nothing to install.
get_replicaset_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 get_replicaset_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 get_replicaset_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.
get_replicaset_pods 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 →