Create a delete intent for a mailbox. This is step 1 of the two-step deletion process. Returns an intent with a confirmation token that expires in 5 minutes. The intent must be confirmed with confirm_delete_intent to proceed.
AI agents call create_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.
Although this is only step 1 of a two-step deletion process and does not itself delete anything, it is part of an irreversible destructive workflow (mailbox deletion). The most severe applicable category for a deletion-initiation tool is Destructive. Severity is medium rather than high because the actual deletion requires a separate confirmation step, limiting immediate blast radius from this tool alone.
From the tool's definition 'Create a delete intent for a mailbox' and 'two-step deletion process' — this initiates an irreversible deletion workflow for a mailbox
Attacks that exploit this kind of access
Create a delete intent for a mailbox. This is step 1 of the two-step deletion process. Returns an intent with a confirmation token that expires in 5 minutes. The intent must be confirmed with confirm_delete_intent to proceed. 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 create_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.
create_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 create_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 create_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.
create_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 →