cluster_auto_upgrade_config · GreenNode MCP Server MCP

WHAT IT DOES

What cluster_auto_upgrade_config does on GreenNode MCP Server

AI agents use cluster_auto_upgrade_config 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 cluster_auto_upgrade_config needs a policy

The name implies configuring auto-upgrade settings for a cluster, which is a Write operation (modifying configuration). The sibling 'cluster_auto_upgrade_delete' exists separately for deletion, reinforcing that this tool likely updates/sets upgrade configuration. Severity is high because misconfiguring auto-upgrade on a Kubernetes cluster could trigger unintended upgrades affecting production workloads.

From the tool's definition Tool name 'cluster_auto_upgrade_config' — the 'config' suffix suggests writing/updating configuration rather than deletion or execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cluster_auto_upgrade_config Rate-limited

cluster_auto_upgrade_config 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": {
    "cluster_auto_upgrade_config": {
      "limits": [
        {
          "counter": "cluster_auto_upgrade_config_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 cluster_auto_upgrade_config

What does the cluster_auto_upgrade_config tool do? +

cluster_auto_upgrade_config. 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 cluster_auto_upgrade_config? +

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

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

Can I rate-limit cluster_auto_upgrade_config? +

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

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

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