nodegroup_update · GreenNode MCP Server MCP: Risk & Policy

WHAT IT DOES

What nodegroup_update does on GreenNode MCP Server

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

WHY IT NEEDS A POLICY

Why nodegroup_update needs a policy

The name 'nodegroup_update' strongly implies modifying an existing Kubernetes node group configuration. Updates to node groups can affect cluster capacity, autoscaling, and workloads, making this a high-severity Write operation. However, confidence is reduced to 0.5 due to the empty description providing no explicit confirmation of behavior.

From the tool's definition Tool name 'nodegroup_update' on a server managing VNG Cloud infrastructure including Kubernetes resources

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nodegroup_update Rate-limited

nodegroup_update 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": {
    "nodegroup_update": {
      "limits": [
        {
          "counter": "nodegroup_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_update

What does the nodegroup_update tool do? +

nodegroup_update. It is categorised as a Write tool in the GreenNode 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 nodegroup_update? +

Register the GreenNode MCP Server MCP server in PolicyLayer and add a rule for nodegroup_update: 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_update? +

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

Can I rate-limit nodegroup_update? +

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

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

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