get_cluster
Gets the details of a specific GKE cluster.
This record as markdown: /tools/com-googleapis-container-mcp/get-cluster.md
What get_cluster does on Mcp
AI agents call get_cluster 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 |
|---|---|---|---|
name | string | Yes | Required. The name (project, location, cluster) of the cluster to retrieve. Specified in the format `projects/*/locations/*/clusters/*`. |
readMask | string | — | Optional. The field mask to specify the fields to be returned in the response. Use a single "*" to get all fields. Default: autopilot,createTime,currentMasterVe |
Parameters from the server's own tool schema.
Why get_cluster is rated Low
This tool retrieves and returns cluster information (name, configuration, status, etc.) without creating, modifying, deleting, or executing operations. It is a pure query operation with no side effects. Even if an AI agent misuses it by requesting sensitive cluster details, the blast radius is limited to information disclosure—no resources are altered or destroyed.
From the tool's definition Tool name 'get_cluster' and description 'Gets the details of a specific GKE cluster' indicate retrieval of cluster metadata without modification.
Attacks that exploit this kind of access
The rule that runs get_cluster 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 get_cluster, this is the rule to start with:
get_cluster 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 get_cluster call is checked against it from then on.
Questions about get_cluster
Gets the details of a specific GKE cluster. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_cluster accepts 2 parameters: name, readMask. Required: name. 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 get_cluster: 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.
get_cluster 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_cluster 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_cluster. 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_cluster 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