Get all common resources in a namespace
AI agents call k8s_get_all 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 queries and lists Kubernetes resources (pods, services, deployments, etc.) in a namespace. It performs no side effects, creates no resources, executes no commands, and modifies nothing. It is a pure read operation that gathers information about cluster state. The 'Get' verb and retrieval-focused description clearly position this as a Read category tool with low severity risk.
From the tool's definition Tool name 'k8s_get_all' and description 'Get all common resources in a namespace' indicate a retrieval operation with the verb 'Get', which retrieves cluster state without modification.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Get all common resources in a namespace. 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 k8s_get_all: 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.
k8s_get_all 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_get_all 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_get_all. 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_get_all is provided by the Kubernetes MCP Server MCP server (mjrestivo16/mcp-kubernetes). 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 →