AI agents call gandi_livedns_get_dnssec_key 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 retrieves (gets) a DNSSEC key by its identifier. It performs a query operation with no side effects—it does not create, modify, delete, or execute any actions. DNSSEC keys are cryptographic public information used for DNS security, and reading them poses minimal risk. Classified as Read with low severity due to the informational nature of the operation.
From the tool's definition Tool name 'gandi_livedns_get_dnssec_key' and description 'Get a single LiveDNS DNSSEC key by id' indicate a retrieval operation with no modification.
Attacks that exploit this kind of access
Get a single LiveDNS DNSSEC key by id. 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_livedns_get_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_get_dnssec_key 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_livedns_get_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_get_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_get_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 →