list_clusters
Lists GKE clusters in a given project and location. Location can be a region, zone, or '-' for all locations.
This record as markdown: /tools/com-googleapis-container-mcp/list-clusters.md
What list_clusters does on Mcp
AI agents call list_clusters to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
parent | string | Yes | Required. The parent (project and location) where the clusters will be listed. Specified in the format `projects/*/locations/*`. Location "-" matches all zones |
readMask | string | — | Optional. The field mask to specify the fields to be returned in the response. Use a single "*" to get all fields. Default: clusters.autopilot,clusters.createTi |
Parameters from the server's own tool schema.
Why list_clusters is rated Low
This tool retrieves information about existing Kubernetes clusters without creating, modifying, deleting, or executing any operations. It is a pure query operation that returns cluster metadata. The blast radius is minimal as an AI agent cannot cause damage by listing clusters—it can only enumerate infrastructure that already exists.
From the tool's definition Tool name 'list_clusters' and description 'Lists GKE clusters in a given project and location' indicate data retrieval with no modification. Server description also confirms 'read access to your GKE and Kubernetes resources.'
Attacks that exploit this kind of access
The rule that runs list_clusters safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_clusters, this is the rule to start with:
list_clusters is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every list_clusters call is checked against it from then on.
Questions about list_clusters
Lists GKE clusters in a given project and location. Location can be a region, zone, or '-' for all locations. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
list_clusters accepts 2 parameters: parent, readMask. Required: parent. The full parameter table on this page comes from the server's own tool schema.
Register the 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 Mcp. 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 MCP server (https://container.googleapis.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue