Lists all namespaces in the cluster
AI agents call list-namespaces to retrieve information from K8s Doctor MCP 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 enumeration of Kubernetes namespaces. It has no side effects, cannot execute code, and cannot modify or delete resources. The blast radius is minimal—at worst an agent learns the namespace structure of a cluster. It aligns with the Read category pattern (list, fetch operations).
From the tool's definition Tool name 'list-namespaces' and description 'Lists all namespaces in the cluster' indicate a query operation that retrieves cluster metadata without modifying or executing anything.
Attacks that exploit this kind of access
Lists all namespaces in the cluster. It is categorised as a Read tool in the K8s Doctor MCP MCP Server, which means it retrieves data without modifying state.
Register the K8s Doctor MCP server in PolicyLayer and add a rule for list-namespaces: 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 K8s Doctor MCP. Nothing to install.
list-namespaces 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 list-namespaces 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 list-namespaces. 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.
list-namespaces is provided by the K8s Doctor MCP server (ongjin/k8s-doctor-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 →