nodegroup_delete
AI agents call nodegroup_delete to permanently remove resources in GreenNode MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool name explicitly indicates a delete operation on node groups (compute resources in Kubernetes clusters). Node group deletion is an irreversible action that terminates compute resources and cannot be undone. This falls into the Destructive category with critical severity due to the potential to destroy production infrastructure and associated workloads.
From the tool's definition Tool name is 'nodegroup_delete' and sibling tools include 'cluster_delete' and 'cluster_delete_dryrun', indicating this performs irreversible deletion of infrastructure resources. The server manages VNG Cloud infrastructure including compute resources.
Attacks that exploit this kind of access
nodegroup_delete. It is categorised as a Destructive tool in the GreenNode MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GreenNode MCP Server MCP server in PolicyLayer and add a rule for nodegroup_delete: 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 is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the nodegroup_delete 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. 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 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 →