update_kubernetes_node_pool

Update an existing node pool in a Kubernetes cluster

SERVERLinode MCP Server SOURCEtakashito/linode-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/takashito-linode-mcp-server/update-kubernetes-node-pool.md

WHAT IT DOES

What update_kubernetes_node_pool does on Linode MCP Server

AI agents use update_kubernetes_node_pool to create or update resources in Linode MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linode MCP Server environment.

RISK

Why update_kubernetes_node_pool is rated Medium

This tool modifies infrastructure state reversibly—node pool configurations can be adjusted, reverted, or updated again. It does not delete resources (Destructive), execute arbitrary commands (Execute), or transfer money (Financial). However, it carries high severity because misconfigured node pools can disrupt cluster operations, cause workload failures, or compromise resource isolation.

From the tool's definition Tool name 'update_kubernetes_node_pool' and description 'Update an existing node pool in a Kubernetes cluster' indicate modification of infrastructure configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_kubernetes_node_pool safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_kubernetes_node_pool, this is the rule to start with:

update_kubernetes_node_pool Rate-limited

update_kubernetes_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_kubernetes_node_pool": {
      "limits": [
        {
          "counter": "update_kubernetes_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 Linode MCP Server, apply this rule, and every update_kubernetes_node_pool call is checked against it from then on.

FAQ

Questions about update_kubernetes_node_pool

What does the update_kubernetes_node_pool tool do? +

Update an existing node pool in a Kubernetes cluster. It is categorised as a Write tool in the Linode MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_kubernetes_node_pool? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for update_kubernetes_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 Linode MCP Server. Nothing to install.

What risk level is update_kubernetes_node_pool? +

update_kubernetes_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_kubernetes_node_pool? +

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

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

update_kubernetes_node_pool is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Linode MCP Server, and thousands of servers like it.

This server

All 416 Linode MCP Server tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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