AI agents call gandi_livedns_list_tsig_keys 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 is fundamentally a Read operation as it retrieves existing TSIG keys without modifying them. However, severity is elevated to 'medium' rather than 'low' because TSIG keys are authentication credentials that could be exploited if exposed to an unauthorized agent—misuse could enable unauthorized DNS zone transfers. The tool itself is safe, but the sensitivity of the data it returns justifies medium severity.
From the tool's definition Tool name indicates 'list' operation which retrieves data; description states 'List AXFR TSIG keys' - a query operation with no modification or deletion.
Attacks that exploit this kind of access
List AXFR TSIG keys for the account. 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_tsig_keys: 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_tsig_keys 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_tsig_keys 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_tsig_keys. 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_tsig_keys 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 →