get_namespaces

List all namespaces in the cluster

Server Kubernetes + Prometheus SRE MCP Server manishmaurya22/sre-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_namespaces does on Kubernetes + Prometheus SRE MCP Server

AI agents call get_namespaces to retrieve information from Kubernetes + Prometheus SRE MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_namespaces needs a policy

This tool retrieves cluster namespace information without side effects. While classified as Read (no modifications), severity is medium rather than low because namespace enumeration in Kubernetes exposes cluster structure and partition boundaries that could inform lateral movement or reconnaissance by a compromised agent. In a multi-tenant cluster, namespace names may reveal sensitive organizational information.

From the tool's definition Tool name 'get_namespaces' with description 'List all namespaces in the cluster' indicates a query/retrieval operation. The verb 'List' and action of fetching namespace information confirms read-only behavior with no data modification or deletion.

Questions about get_namespaces

What does the get_namespaces tool do? +

List all namespaces in the cluster. It is categorised as a Read tool in the Kubernetes + Prometheus SRE MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_namespaces? +

Register the Kubernetes + Prometheus SRE MCP Server MCP server in PolicyLayer and add a rule for get_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 Kubernetes + Prometheus SRE MCP Server. Nothing to install.

What risk level is get_namespaces? +

get_namespaces is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_namespaces? +

Yes. Add a rate_limit block to the get_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.

How do I block get_namespaces completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_namespaces? +

get_namespaces is provided by the Kubernetes + Prometheus SRE MCP Server MCP server (manishmaurya22/sre-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.