List Kubernetes pods with optional namespace, label and NF-type filters.
AI agents call tool_k8s_get_pods to retrieve information from Kubernetes MCP Server – 5G Core Edition without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns Kubernetes pod information without modifying state, executing code, or triggering side effects. It is a pure read operation analogous to 'kubectl get pods'. The optional filters (namespace, label, NF-type) are parameters for scoping the query, not for executing arbitrary commands.
From the tool's definition Tool name 'k8s_get_pods' and description 'List Kubernetes pods' indicates a retrieval operation with optional filtering by namespace, label, and NF-type. No mutation, deletion, or execution capability.
Attacks that exploit this kind of access
List Kubernetes pods with optional namespace, label and NF-type filters. It is categorised as a Read tool in the Kubernetes MCP Server – 5G Core Edition MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes MCP Server – 5G Core Edition MCP server in PolicyLayer and add a rule for tool_k8s_get_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 – 5G Core Edition. Nothing to install.
tool_k8s_get_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 tool_k8s_get_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 tool_k8s_get_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.
tool_k8s_get_pods is provided by the Kubernetes MCP Server – 5G Core Edition MCP server (sanzco/mcp5g). 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 →