Delete a LiveDNS DNSSEC key.
AI agents call gandi_livedns_delete_dnssec_key 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 irreversibly removes DNSSEC keys, which are essential cryptographic components for securing DNS resolution. Deletion cannot be undone and impacts the security posture of domains. This makes it Destructive rather than Write.
From the tool's definition The tool name explicitly states 'delete' and the description confirms it performs 'Delete a LiveDNS DNSSEC key.' DNSSEC keys are critical security infrastructure for DNS, and deletion is irreversible.
Attacks that exploit this kind of access
Delete a LiveDNS DNSSEC key. 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_dnssec_key: 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_dnssec_key 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_dnssec_key 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_dnssec_key. 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_dnssec_key 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 →