empty_folder
Delete all messages in Trash or Junk folder. Only these two folders can be emptied. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true.
This record as markdown: /tools/trekmail-mcp-server/empty-folder.md
What empty_folder does on TrekMail MCP Server
AI agents call empty_folder 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 empty_folder is rated Critical
This tool permanently and irreversibly deletes all messages in specified folders (Trash or Junk). The deletion is bulk, non-recoverable, and the API explicitly requires a destructive operations flag, indicating the developers classified this as a high-risk irreversible operation. While scoped to two folders, the blast radius for an agent incorrectly targeting this tool is complete data loss within those folders.
From the tool's definition 'Delete all messages' with explicit destructive confirmation requirement 'Requires TREKMAIL_ALLOW_DESTRUCTIVE=true' and irreversible action on message data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs empty_folder 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 empty_folder, this is the rule to start with:
empty_folder 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 empty_folder call is checked against it from then on.
Questions about empty_folder
Delete all messages in Trash or Junk folder. Only these two folders can be emptied. Requires 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 empty_folder: 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.
empty_folder 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 empty_folder 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 empty_folder. 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.
empty_folder 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