Get details of a specific node pool in a GKE cluster.
AI agents call get_gke_node_pool 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 queries and retrieves information about Kubernetes node pool configuration without making any changes to the cluster, nodes, or workloads. The operation is read-only with no side effects. Blast radius is minimal—exposing node pool details to an AI agent poses low risk since it cannot use this information alone to compromise the cluster.
From the tool's definition Tool name and description indicate retrieval of node pool details: 'Get details of a specific node pool'. The sibling tools (get_gke_cluster, get_gke_server_config, list_*) are all read operations.
Attacks that exploit this kind of access
Get details of a specific node pool 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 get_gke_node_pool: 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.
get_gke_node_pool 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_gke_node_pool 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_gke_node_pool. 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_gke_node_pool 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 →