confirm_delete_intent
Confirm a delete intent to delete a mailbox. This is step 2 of the two-step deletion process. The mailbox is moved to the recycle bin and can be restored within the retention window (default 7 days) with restore_mailbox; after that window it is permanently purged. Both TREKMAIL_ALLOW_DESTRUCTIVE=...
This record as markdown: /tools/trekmail-mcp-server/confirm-delete-intent.md
What confirm_delete_intent does on TrekMail MCP Server
AI agents call confirm_delete_intent to permanently remove resources in TrekMail MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why confirm_delete_intent is rated Critical
This tool irreversibly deletes mailboxes (moves to recycle bin with eventual permanent purge), which is the hallmark of the Destructive category. While there is a 7-day restoration window, the tool's primary function is deletion, and permanent purging after that window means data loss is irreversible long-term.
From the tool's definition Tool description explicitly states it 'delete[s] a mailbox' and 'permanently purged' after retention window. The confirmation requirement and two-step process indicate high-risk irreversible action. Mailbox deletion cannot be undone after retention expires.
Attacks that exploit this kind of access
The rule that runs confirm_delete_intent safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For confirm_delete_intent, this is the rule to start with:
confirm_delete_intent 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 TrekMail MCP Server, apply this rule, and every confirm_delete_intent call is checked against it from then on.
Questions about confirm_delete_intent
Confirm a delete intent to delete a mailbox. This is step 2 of the two-step deletion process. The mailbox is moved to the recycle bin and can be restored within the retention window (default 7 days) with restore_mailbox; after that window it is permanently purged. Both TREKMAIL_ALLOW_DESTRUCTIVE=true and confirm=true are required. It is categorised as a Destructive tool in the TrekMail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for confirm_delete_intent: 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 TrekMail MCP Server. Nothing to install.
confirm_delete_intent 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 confirm_delete_intent 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 confirm_delete_intent. 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.
confirm_delete_intent is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TrekMail MCP Server, and thousands of servers like it.
Across the catalogue