AI agents call get_namespaces to retrieve information from Kubernetes Monitor without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Kubernetes namespace information without modifying state. Even though the description is empty, the server's stated read-only purpose and the consistent pattern of sibling tools (all query/list operations) strongly indicate this is a safe read operation. The blast radius of namespace enumeration is minimal—it only exposes cluster topology information useful for diagnosis.
From the tool's definition Tool is part of a 'read-only MCP server for Kubernetes' and belongs among sibling tools like 'list_deployments', 'list_pods', 'list_services', and 'list_nodes', which are all query/listing operations.
Documented attack patterns abuse exactly the kind of access get_namespaces gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kubernetes Monitor, and nothing reaches the server without passing your rules. This is the rule we recommend for get_namespaces:
{
"version": "1",
"default": "deny",
"tools": {
"get_namespaces": {}
}
}get_namespaces is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_namespaces. It is categorised as a Read tool in the Kubernetes Monitor MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes Monitor 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 Monitor. Nothing to install.
get_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 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.
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.
get_namespaces is provided by the Kubernetes Monitor MCP server (vlttnv/k8s-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kubernetes Monitor, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Kubernetes Monitor tools catalogued and risk-classified — across an index of 43,000+ MCP servers.