nodegroup_delete_dryrun
AI agents invoke nodegroup_delete_dryrun 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.
The 'dryrun' suffix strongly implies this tool simulates a nodegroup deletion without actually performing it, similar to 'cluster_delete_dryrun' on the same server. Dry-run operations are typically read-like in effect (they preview what would happen) but involve execution of validation/planning logic. Since no actual deletion occurs, it doesn't qualify as Destructive.
From the tool's definition Tool name 'nodegroup_delete_dryrun' — 'dryrun' suffix suggests a simulation/preview of a delete operation rather than an actual deletion.
Attacks that exploit this kind of access
nodegroup_delete_dryrun. 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.
Register the GreenNode MCP Server MCP server in PolicyLayer and add a rule for nodegroup_delete_dryrun: 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.
nodegroup_delete_dryrun is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the nodegroup_delete_dryrun 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.
Set action: deny in the PolicyLayer policy for nodegroup_delete_dryrun. 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.
nodegroup_delete_dryrun 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →