AI agents call gandi_domain_get_contacts 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 retrieves existing contact information associated with a domain. It performs no mutations, deletions, financial transactions, or code execution. The operation is a straightforward data retrieval with minimal blast radius if misused by an AI agent, as it only exposes contact details already associated with the domain.
From the tool's definition Tool name contains 'get' and description states it retrieves 'Current contact block (admin/tech/bill/owner) for a domain' — a read-only query operation with no side effects or data modification.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Current contact block (admin/tech/bill/owner) 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_contacts: 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_contacts 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_contacts 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_contacts. 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_contacts 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 →