AI agents use gandi_email_update_offer 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.
The tool performs an update operation on email offerings, which modifies data (Write category). Severity is high because email service changes can affect multiple users' communication capabilities and access to services. Confidence is lowered to 0.75 due to empty description preventing verification of exact parameters and scope of the update operation.
From the tool's definition Tool name 'gandi_email_update_offer' indicates modification of email service offerings. The 'update' verb combined with email service context suggests reversible changes to email configurations or plans.
Attacks that exploit this kind of access
gandi_email_update_offer. 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_email_update_offer: 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_email_update_offer 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_email_update_offer 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_email_update_offer. 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_email_update_offer 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 →