cluster_create_validate · GreenNode MCP Server MCP

WHAT IT DOES

What cluster_create_validate does on GreenNode MCP Server

AI agents invoke cluster_create_validate 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 cluster_create_validate needs a policy

With no description, classification relies on the name alone. 'validate' strongly suggests a read-like pre-flight check (no actual resource creation), similar to the sibling 'cluster_delete_dryrun'. However, it could trigger external validation operations. Given the ambiguity and empty description, Execute is chosen conservatively, but confidence is low.

From the tool's definition Tool name 'cluster_create_validate' — description is empty/uninformative. Based on name, likely validates a cluster creation request (a dry-run or pre-flight check) rather than actually creating a cluster.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cluster_create_validate Rate-limited

cluster_create_validate 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": {
    "cluster_create_validate": {
      "limits": [
        {
          "counter": "cluster_create_validate_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 cluster_create_validate

What does the cluster_create_validate tool do? +

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

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

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

Can I rate-limit cluster_create_validate? +

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

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

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