List services in a namespace or all namespaces
AI agents call k8s_list_services 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 performs a read-only operation (list/query) on Kubernetes services. It has no side effects—it neither creates, modifies, deletes, nor executes any operations. The blast radius is minimal as it only exposes existing service metadata. While it may reveal cluster topology information, this is a standard informational query with no destructive or operational capability.
From the tool's definition Tool name 'k8s_list_services' and description 'List services in a namespace or all namespaces' indicate a query operation that retrieves information without modifying cluster state.
Attacks that exploit this kind of access
List services in a namespace or all namespaces. 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_list_services: 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_list_services 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_list_services 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_list_services. 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_list_services 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 →