email_delete
Move an email message to trash. Subject to mailbox grant permissions. This is a soft delete (trash), not permanent.
This record as markdown: /tools/flowdot-llc-mcp-server/email-delete.md
What email_delete does on FlowDot MCP Server
AI agents call email_delete to permanently remove resources in FlowDot MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why email_delete is rated Critical
Although technically recoverable from trash, email deletion is functionally destructive because: (1) it removes data from active use; (2) the action cannot be undone with a simple reversal—recovery requires accessing the trash folder; (3) if the trash is auto-purged or the user empties it, deletion becomes permanent; (4) an AI agent misusing this tool could delete critical business emails, causing operational and…
From the tool's definition Tool name is 'email_delete' and description states 'Move an email message to trash'. While described as a 'soft delete', the action irreversibly removes the email from the user's active mailbox and primary workflow, which constitutes data loss from the user's…
Attacks that exploit this kind of access
The rule that runs email_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FlowDot MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email_delete, this is the rule to start with:
email_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FlowDot MCP Server, apply this rule, and every email_delete call is checked against it from then on.
Questions about email_delete
Move an email message to trash. Subject to mailbox grant permissions. This is a soft delete (trash), not permanent. It is categorised as a Destructive tool in the FlowDot MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the FlowDot MCP Server MCP server in PolicyLayer and add a rule for email_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 FlowDot MCP Server. Nothing to install.
email_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 email_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 email_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.
email_delete is provided by the FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
Across the catalogue