AI agents invoke gandi_domain_relaunch_reachability to trigger actions in Gandi. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation — relaunching a contact-validation/reachability check process. It doesn't merely read data, nor does it create/modify persistent data in a reversible way or delete anything. It initiates an external workflow or verification process, making Execute the most appropriate category. Misuse could cause repeated validation emails/notifications to registrants, hence medium severity.
From the tool's definition Relaunch the registrant reachability (contact-validation) check
Attacks that exploit this kind of access
Relaunch the registrant reachability (contact-validation) check. It is categorised as a Execute tool in the Gandi MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gandi MCP server in PolicyLayer and add a rule for gandi_domain_relaunch_reachability: 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_relaunch_reachability is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gandi_domain_relaunch_reachability 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_relaunch_reachability. 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_relaunch_reachability 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 →