create_node_pool
Creates a node pool for a specific GKE cluster.
This record as markdown: /tools/com-googleapis-container-mcp/create-node-pool.md
What create_node_pool does on Mcp
AI agents use create_node_pool to create or update resources in Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
parent | string | Yes | Required. The parent (project, location, cluster name) where the node pool will be created. Specified in the format `projects/*/locations/*/clusters/*`. |
nodePool | string | Yes | Required. The node pool to create represented as a string using JSON format. The full node pool object can be found at https://docs.cloud.google.com/kubernetes- |
Parameters from the server's own tool schema.
Why create_node_pool is rated Medium
Creating a node pool modifies cluster infrastructure by adding compute capacity. While reversible (via delete_k8s_resource), it has significant blast radius: an AI agent could rapidly scale up cluster costs, consume quotas, or create resource exhaustion. This is Write rather than Execute because the operation itself is a straightforward resource creation, not arbitrary code execution.
From the tool's definition Tool name 'create_node_pool' directly indicates creation of a new resource. Description states 'Creates a node pool for a specific GKE cluster.' This is a reversible modification operation.
Attacks that exploit this kind of access
The rule that runs create_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 create_node_pool, this is the rule to start with:
create_node_pool stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 create_node_pool call is checked against it from then on.
Questions about create_node_pool
Creates a node pool for a specific GKE cluster. It is categorised as a Write tool in the Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_node_pool accepts 2 parameters: parent, nodePool. Required: parent, nodePool. 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 create_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.
create_node_pool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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