nodegroup_upgrade_version · GreenNode MCP Server MCP

WHAT IT DOES

What nodegroup_upgrade_version does on GreenNode MCP Server

AI agents invoke nodegroup_upgrade_version to trigger actions in GreenNode MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why nodegroup_upgrade_version needs a policy

Based on the tool name, this appears to upgrade the version of a node group in a Kubernetes cluster. Version upgrades are Execute-level operations as they trigger external operations (rolling updates, node replacements) that can affect running workloads. The blast radius is high since upgrading node groups in production Kubernetes clusters can disrupt services. Confidence is low due to empty description.

From the tool's definition Tool name 'nodegroup_upgrade_version' — no description provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nodegroup_upgrade_version Rate-limited

nodegroup_upgrade_version stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "nodegroup_upgrade_version": {
      "limits": [
        {
          "counter": "nodegroup_upgrade_version_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GreenNode MCP Server, so you can run agents against it safely.

FAQ

Questions about nodegroup_upgrade_version

What does the nodegroup_upgrade_version tool do? +

nodegroup_upgrade_version. It is categorised as a Execute tool in the GreenNode MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on nodegroup_upgrade_version? +

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

What risk level is nodegroup_upgrade_version? +

nodegroup_upgrade_version is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit nodegroup_upgrade_version? +

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

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

nodegroup_upgrade_version is provided by the GreenNode MCP Server MCP server (vngcloud/greennode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.