Delete a message. By default moves to Trash (recoverable). Pass hardDelete=true to permanently delete — not recoverable.
AI agents call gmail_delete to permanently remove resources in Personal Gmail — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While the default behavior (moving to Trash) is reversible and would be Write category, the tool's explicit support for permanent, non-recoverable deletion via the hardDelete parameter makes it Destructive. Even though recovery is possible by default, the capability for irreversible data destruction is the primary security concern.
From the tool's definition Tool description explicitly states 'Pass hardDelete=true to permanently delete — not recoverable.' The hardDelete parameter enables irreversible deletion of email messages.
Attacks that exploit this kind of access
Delete a message. By default moves to Trash (recoverable). Pass hardDelete=true to permanently delete — not recoverable. It is categorised as a Destructive tool in the Personal Gmail MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Personal Gmail MCP server in PolicyLayer and add a rule for gmail_delete: 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 Personal Gmail. Nothing to install.
gmail_delete 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 gmail_delete 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 gmail_delete. 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.
gmail_delete is provided by the Personal Gmail MCP server (jaingxyz/personal-gmail-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 →