Delete an entire thread and all its messages
AI agents call mail_delete_thread to permanently remove resources in Mailgent 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 data (an entire thread and all associated messages). Deletion is irreversible and constitutes a destructive action. The blast radius is high because an AI agent could maliciously or accidentally delete important email threads, conversations, and their full message history.
From the tool's definition Tool name is 'mail_delete_thread' and description states 'Delete an entire thread and all its messages' — this irreversibly removes data with no undo mechanism.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete an entire thread and all its messages. It is categorised as a Destructive tool in the Mailgent MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mailgent MCP Server MCP server in PolicyLayer and add a rule for mail_delete_thread: 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 Mailgent MCP Server. Nothing to install.
mail_delete_thread 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 mail_delete_thread 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 mail_delete_thread. 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.
mail_delete_thread is provided by the Mailgent MCP Server MCP server (loomal-ai/loomal-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 →