New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_node_pool

Gets the details of a specific node pool within a GKE cluster.

SERVERMcp SOURCEhttps://container.googleapis.com/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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.

Questions about get_node_pool

What does the get_node_pool tool do? +

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.

What parameters does get_node_pool accept? +

get_node_pool accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_node_pool? +

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.

What risk level is get_node_pool? +

get_node_pool is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_node_pool? +

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.

How do I block get_node_pool completely? +

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.

What MCP server provides get_node_pool? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.