AI agents use gandi_linkedzone_update_zone 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 zone data reversibly, fitting the Write category. Severity is high because misconfiguration of DNS zones can disrupt domain resolution, email delivery, and service availability, affecting production infrastructure and potentially multiple dependent systems. However, it is not Destructive (zones are not deleted) and not Financial.
From the tool's definition Tool name 'gandi_linkedzone_update_zone' indicates modification of a linked zone configuration. The verb 'update' explicitly denotes a write operation that modifies existing DNS/zone data.
Attacks that exploit this kind of access
Update a linked zone. 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_linkedzone_update_zone: 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_linkedzone_update_zone 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_linkedzone_update_zone 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_linkedzone_update_zone. 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_linkedzone_update_zone 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 →