AI agents use gandi_domain_update_contacts to create or update resources in Gandi — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gandi environment.
This tool creates or modifies contact data associated with domains—a classic Write operation. While reversible (contacts can be updated again), modifying domain contacts is high-severity because it affects administrative control and legal responsibility for domains. The lack of description prevents higher confidence, but the name clearly indicates a Write action within a domain management context.
From the tool's definition Tool name 'gandi_domain_update_contacts' indicates modification of domain contact information. The 'update' verb combined with 'contacts' on a domain management server shows reversible data modification.
Attacks that exploit this kind of access
gandi_domain_update_contacts. It is categorised as a Write tool in the Gandi MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gandi MCP server in PolicyLayer and add a rule for gandi_domain_update_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_update_contacts is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gandi_domain_update_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_update_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_update_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 →