List node pools in a GKE cluster.
AI agents call list_gke_node_pools to retrieve information from Google Cloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates node pool information from a GKE cluster without creating, modifying, or deleting resources. Listing operations are foundational Read operations with minimal blast radius—the worst outcome of misuse would be information disclosure about cluster infrastructure, which is low severity in comparison to Write, Execute, or Destructive actions.
From the tool's definition Tool name 'list_gke_node_pools' and description 'List node pools in a GKE cluster' indicate a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
List node pools in a GKE cluster. It is categorised as a Read tool in the Google Cloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Cloud MCP Server MCP server in PolicyLayer and add a rule for list_gke_node_pools: 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 Google Cloud MCP Server. Nothing to install.
list_gke_node_pools 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_node_pools 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_node_pools. 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_node_pools is provided by the Google Cloud MCP Server MCP server (nsachin08/gcpmcp). 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 →