Immediately and permanently delete a message
AI agents call delete_message to permanently remove resources in Gmail MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes email messages without recovery options. Destructive is the appropriate category because the action cannot be undone and results in data loss. Severity is high because an AI agent could inadvertently delete important emails, attachments, or entire conversations, impacting user communications and potentially causing business or legal harm.
From the tool's definition Tool name 'delete_message' combined with description 'Immediately and permanently delete a message' explicitly indicates irreversible deletion of email data.
Attacks that exploit this kind of access
Immediately and permanently delete a message. It is categorised as a Destructive tool in the Gmail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for delete_message: 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 Gmail MCP Server. Nothing to install.
delete_message 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 delete_message 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 delete_message. 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.
delete_message is provided by the Gmail MCP Server MCP server (nk900600/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 →