Delete a snapshot
AI agents call delete_snapshot 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.
Snapshots are critical backup artifacts used for disaster recovery and data protection. Deleting a snapshot removes a recovery point that cannot be restored. This operation is irreversible and could result in data loss if no other backups exist. The action matches the Destructive category as it permanently removes data/backups.
From the tool's definition Tool name 'delete_snapshot' and description 'Delete a snapshot' explicitly indicate irreversible deletion of data. The verb 'delete' combined with 'snapshot' (a point-in-time backup copy) demonstrates permanent removal of a backup artifact.
Attacks that exploit this kind of access
Delete a snapshot. 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_snapshot: 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_snapshot 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_snapshot 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_snapshot. 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_snapshot 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 →