List all namespaces in the Kubernetes cluster.
AI agents call list_namespaces to retrieve information from Lumino 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 cluster metadata (namespaces) without modifying, executing, or deleting anything. It is a straightforward read operation with minimal risk—discovering namespaces is typically non-sensitive cluster enumeration. Severity is low because the information is generally available to authenticated cluster users and the operation has no side effects.
From the tool's definition Tool name is 'list_namespaces' and description states 'List all namespaces in the Kubernetes cluster.' The verb 'list' and action of querying/retrieving namespace information with no modifications indicate a read-only operation.
Attacks that exploit this kind of access
List all namespaces in the Kubernetes cluster. It is categorised as a Read tool in the Lumino MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lumino MCP Server 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 Lumino MCP Server. 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 Lumino MCP Server MCP server (lumino-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 →