AI agents call gandi_livedns_list_rrtypes 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 only queries and returns informational data about what DNS record types are supported by the LiveDNS service. It performs no writes, deletes, executions, or financial operations. The blast radius of misuse is minimal since it only reveals schema/reference information that is typically public. Classified as Read with low severity.
From the tool's definition Tool name contains 'list' and description states 'List DNS record types' - a retrieval operation with no modification or side effects. Returns static reference data (A, AAAA, CNAME, MX, etc.) about accepted DNS record types.
Attacks that exploit this kind of access
List DNS record types accepted by LiveDNS (A, AAAA, CNAME, MX, etc.). 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_list_rrtypes: 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_list_rrtypes 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_list_rrtypes 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_list_rrtypes. 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_list_rrtypes 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 →