AI agents call gandi_domain_get_livedns_dnssec to retrieve information from Gandi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns DNSSEC status information for a domain. The 'get' verb and passive framing ('state for a domain') indicate read-only data retrieval. No creation, modification, deletion, code execution, or financial operations are implied. The blast radius of misuse is minimal — exposing DNS security settings poses no direct harm to infrastructure or finances.
From the tool's definition Tool name contains 'get' and description states 'DNSSEC state for a domain' — retrieves DNS security configuration without modifying data.
Attacks that exploit this kind of access
LiveDNS-managed DNSSEC state for a domain. It is categorised as a Read tool in the Gandi MCP Server, which means it retrieves data without modifying state.
Register the Gandi MCP server in PolicyLayer and add a rule for gandi_domain_get_livedns_dnssec: 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_domain_get_livedns_dnssec is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gandi_domain_get_livedns_dnssec 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_domain_get_livedns_dnssec. 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_domain_get_livedns_dnssec 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 →