drive_folder_purge
DESTRUCTIVE. Hard-delete a TRASHED folder + its entire subtree. B2 cleanup runs async. Requires drive:*:purge scope AND TREKMAIL_ALLOW_DESTRUCTIVE=true.
This record as markdown: /tools/trekmail-mcp-server/drive-folder-purge.md
What drive_folder_purge does on TrekMail MCP Server
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.
Why drive_folder_purge is rated Critical
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
The rule that runs drive_folder_purge 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 drive_folder_purge, this is the rule to start with:
drive_folder_purge 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 drive_folder_purge call is checked against it from then on.
Questions about drive_folder_purge
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.
More on TrekMail MCP Server, and thousands of servers like it.
Across the catalogue