Confirm a delete intent to permanently delete a mailbox. This is step 2 of the two-step deletion process. IRREVERSIBLE — the mailbox and all its data will be permanently destroyed. Both TREKMAIL_ALLOW_DESTRUCTIVE=true and confirm=true are required.
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.
This tool irreversibly deletes mailboxes and all associated data, which cannot be undone. It meets the Destructive category definition of irreversibly deleting data. The critical severity reflects the extreme blast radius: an AI agent misusing this could permanently destroy entire mailbox systems and all contained messages, contacts, and metadata for users or organizations.
From the tool's definition Tool description explicitly states 'permanently delete a mailbox', 'IRREVERSIBLE — the mailbox and all its data will be permanently destroyed', and requires TREKMAIL_ALLOW_DESTRUCTIVE=true flag, indicating irreversible data destruction.
Attacks that exploit this kind of access
Confirm a delete intent to permanently delete a mailbox. This is step 2 of the two-step deletion process. IRREVERSIBLE — the mailbox and all its data will be permanently destroyed. 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.
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 →