AI agents call list-gke-clusters to retrieve information from GCP MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries GKE cluster metadata and returns a list. It has no side effects, does not modify or delete resources, and does not execute code or operations. It is purely informational retrieval, fitting the Read category. Severity is low because listing clusters reveals infrastructure information but does not expose direct access to clusters or their data.
From the tool's definition Tool name 'list-gke-clusters' and description 'List all GKE clusters in the current project' indicate a read-only operation that retrieves cluster information without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
List all GKE clusters in the current project. It is categorised as a Read tool in the GCP MCP MCP Server, which means it retrieves data without modifying state.
Register the GCP MCP server in PolicyLayer and add a rule for list-gke-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 GCP MCP. Nothing to install.
list-gke-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-gke-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-gke-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-gke-clusters is provided by the GCP MCP server (radiumgu/gcp-ops-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 →