Delete a zone snapshot.
AI agents call gandi_livedns_delete_snapshot to permanently remove resources in Gandi — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on DNS zone snapshots. Zone snapshots are typically critical backups or historical records of DNS configurations. Deleting a snapshot cannot be undone and represents a permanent loss of data. This fits the Destructive category as it irreversibly removes data without recovery options.
From the tool's definition Tool name contains 'delete_snapshot' which indicates irreversible deletion of data. Description confirms: 'Delete a zone snapshot.'
Attacks that exploit this kind of access
Delete a zone snapshot. It is categorised as a Destructive tool in the Gandi MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gandi MCP server in PolicyLayer and add a rule for gandi_livedns_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 Gandi. Nothing to install.
gandi_livedns_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 gandi_livedns_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 gandi_livedns_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.
gandi_livedns_delete_snapshot is provided by the Gandi MCP server (millsymills-com/gandi-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 →