get_node_pool
Gets the details of a specific node pool within a GKE cluster.
This record as markdown: /tools/com-googleapis-container-mcp/get-node-pool.md
What get_node_pool does on Mcp
AI agents call get_node_pool 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, node pool id) of the node pool to get. Specified in the format `projects/*/locations/*/clusters/*/nodePools/*`. |
Parameters from the server's own tool schema.
Why get_node_pool is rated Low
This tool retrieves and returns metadata about a node pool (computational resources in a Kubernetes cluster). It performs no creation, modification, deletion, execution, or financial operations. The verb 'Gets' and the lack of any mutation language confirm this is a read-only query operation. Severity is low because reading cluster configuration details poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_node_pool' and description 'Gets the details of a specific node pool within a GKE cluster' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_node_pool 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_node_pool, this is the rule to start with:
get_node_pool 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_node_pool call is checked against it from then on.
Questions about get_node_pool
Gets the details of a specific node pool within a GKE cluster. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
get_node_pool accepts 1 parameter: name. 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_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 Mcp. Nothing to install.
get_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_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_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_node_pool 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