Delete a mailbox (current mailbox product, not legacy email).
AI agents call gandi_mailbox_delete_mailbox to permanently remove resources in Gandi — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a mailbox, which cannot be undone and results in loss of all associated email data, configurations, and access. While not a financial operation, the destructive nature of removing email infrastructure warrants the Destructive category.
From the tool's definition "Delete a mailbox" - the verb "delete" combined with permanent removal of a mailbox (email account) indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete a mailbox (current mailbox product, not legacy email). It is categorised as a Destructive tool in the Gandi MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gandi MCP server in PolicyLayer and add a rule for gandi_mailbox_delete_mailbox: 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_mailbox_delete_mailbox is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the gandi_mailbox_delete_mailbox 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_mailbox_delete_mailbox. 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_mailbox_delete_mailbox 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 →