DESTRUCTIVE. Hard-delete a TRASHED folder + its entire subtree. B2 cleanup runs async. Requires drive:*:purge scope AND TREKMAIL_ALLOW_DESTRUCTIVE=true.
AI agents call drive_folder_purge 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 permanently and irreversibly deletes a folder and all its contents from storage. There is no undo mechanism described. The explicit DESTRUCTIVE label, hard-delete semantics, async cleanup of B2 storage, and requirement for a destructive-specific environment flag all confirm this is a destructive action with maximum blast radius if triggered unintentionally by an agent.
From the tool's definition Tool name contains 'purge'; description explicitly states 'DESTRUCTIVE', 'Hard-delete', 'entire subtree', and requires TREKMAIL_ALLOW_DESTRUCTIVE=true flag.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
DESTRUCTIVE. Hard-delete a TRASHED folder + its entire subtree. B2 cleanup runs async. Requires drive:*:purge scope AND TREKMAIL_ALLOW_DESTRUCTIVE=true. 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 drive_folder_purge: 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.
drive_folder_purge 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 drive_folder_purge 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 drive_folder_purge. 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.
drive_folder_purge 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 →