update_node_pool

Updates a specific node pool within a GKE cluster.

SERVERMcp SOURCEhttps://container.googleapis.com/mcp

Medium RISK CLASS

Category Write

Parameters 22 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-googleapis-container-mcp/update-node-pool.md

WHAT IT DOES

What update_node_pool does on Mcp

AI agents use update_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
`name`	string	Yes	Required. The name (project, location, cluster, node pool) of the node pool to update. Specified in the format 'projects//locations//clusters//nodePools/'.
`update`	string	Yes	Required. A [node pool update request](https://cloud.google.com/container-engine/reference/rest/v1/projects.locations.clusters.nodePools/update) represented as

Parameters from the server's own tool schema.

RISK

Why update_node_pool is rated Medium

This tool modifies existing GKE infrastructure (node pool configuration) in a way that is reversible and does not permanently delete resources. It falls under Write rather than Execute because it configures managed resources rather than running arbitrary code.

From the tool's definition 'Updates a specific node pool within a GKE cluster' — modifies cluster infrastructure configuration. Node pool updates affect compute resources, autoscaling settings, labels, and other reversible properties.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_node_pool, this is the rule to start with:

update_node_pool Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_node_pool": {
      "limits": [
        {
          "counter": "update_node_pool_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every update_node_pool call is checked against it from then on.

FAQ

Questions about update_node_pool

What does the update_node_pool tool do? +

Updates a specific node pool within a 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.

What parameters does update_node_pool accept? +

update_node_pool accepts 2 parameters: name, update. Required: name, update. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_node_pool? +

Register the MCP server in PolicyLayer and add a rule for update_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 update_node_pool? +

update_node_pool is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_node_pool? +

Yes. Add a rate_limit block to the update_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 update_node_pool completely? +

Set action: deny in the PolicyLayer policy for update_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 update_node_pool? +

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

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 23 tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →