Delete a clone Key Features: - Removes the clone and its associated resources (delete = true) - Can optionally delete the underlying database server (remove = true) Instructions: - Provide the clone ID and specify whether to delete the database server.
AI agents call delete_clone to permanently remove resources in NDB MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes data and resources without the ability to undo the operation. It is destructive by definition as it removes both clones and potentially underlying database servers. The high severity reflects the significant blast radius of accidental deletion of database infrastructure and data in a production Nutanix environment.
From the tool's definition The tool description states it 'Removes the clone and its associated resources (delete = true)' and 'Can optionally delete the underlying database server (remove = true)'. These actions are irreversible deletion operations.
Attacks that exploit this kind of access
Delete a clone Key Features: - Removes the clone and its associated resources (delete = true) - Can optionally delete the underlying database server (remove = true) Instructions: - Provide the clone ID and specify whether to delete the database server. It is categorised as a Destructive tool in the NDB MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the NDB MCP Server MCP server in PolicyLayer and add a rule for delete_clone: 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 NDB MCP Server. Nothing to install.
delete_clone 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 delete_clone 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 delete_clone. 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.
delete_clone is provided by the NDB MCP Server MCP server (rouxton/ndb-mcp-server). 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 →