List all Kubernetes clusters available in kubeconfig
AI agents call list_clusters 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.
This is a straightforward read operation that queries kubeconfig to enumerate available clusters. It has no capability to modify state, execute commands, or affect cluster operations. The blast radius is minimal—disclosure of cluster names is low-risk information typically already known to users with kubeconfig access. Confidence is high because the description is explicit and unambiguous.
From the tool's definition Tool name 'list_clusters' and description 'List all Kubernetes clusters available in kubeconfig' indicate a query/enumeration operation with no side effects. It retrieves configuration information without modifying or executing anything.
Attacks that exploit this kind of access
List all Kubernetes clusters available in kubeconfig. It is categorised as a Read tool in the Kubernetes + Prometheus SRE MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kubernetes + Prometheus SRE MCP Server MCP server in PolicyLayer and add a rule for list_clusters: 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.
list_clusters 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_clusters 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_clusters. 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_clusters 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.
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 →