cluster_delete_dryrun
AI agents call cluster_delete_dryrun 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 name 'cluster_delete_dryrun' strongly implies this performs a dry-run simulation of a cluster deletion operation. While a dry-run itself does not irreversibly delete data, the tool is categorized as Destructive because (1) it is paired with and simulates the behavior of 'cluster_delete', which is irreversible, (2) dry-runs in some platforms do execute partial or preparatory destructive steps, and (3) misuse…
From the tool's definition Tool name contains 'delete' and 'dryrun'; sibling tool 'cluster_delete' confirms deletion context for Kubernetes clusters
Attacks that exploit this kind of access
cluster_delete_dryrun. 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 cluster_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.
cluster_delete_dryrun 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 cluster_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 cluster_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.
cluster_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 →