Delete ALL records under a name (every type).
AI agents call gandi_livedns_delete_named_records 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 permanently removes DNS records without the ability to undo the action. Deleting all records of a name in a DNS system can cause service outages and break email routing, web services, and other critical infrastructure that depends on those records. While not directly financial, the impact is severe (high severity rather than critical due to limited scope within a single name).
From the tool's definition Delete ALL records under a name (every type) — explicitly states deletion of all DNS records, which is irreversible.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete ALL records under a name (every type). 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_named_records: 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_named_records 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_named_records 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_named_records. 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_named_records 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 →