drive_trash_empty
DESTRUCTIVE. Permanently delete every trashed file + folder in the space. Requires drive:*:purge scope AND TREKMAIL_ALLOW_DESTRUCTIVE=true.
This record as markdown: /tools/trekmail-mcp-server/drive-trash-empty.md
What drive_trash_empty does on TrekMail MCP Server
AI agents call drive_trash_empty 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_trash_empty is rated Critical
This tool irreversibly deletes all trashed files and folders. It cannot be undone and has a wide blast radius—an agent with access could remove all organizational data from the trash, causing permanent data loss. The explicit 'DESTRUCTIVE' label and purge scope requirement confirm this is a destructive action, not merely an execute or write operation.
From the tool's definition Tool name 'drive_trash_empty' combined with description explicitly stating 'DESTRUCTIVE. Permanently delete every trashed file + folder in the space.' and requirement for 'drive:*:purge scope AND TREKMAIL_ALLOW_DESTRUCTIVE=true' indicates irreversible…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs drive_trash_empty 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_trash_empty, this is the rule to start with:
drive_trash_empty 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_trash_empty call is checked against it from then on.
Questions about drive_trash_empty
DESTRUCTIVE. Permanently delete every trashed file + folder in the space. 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_trash_empty: 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_trash_empty 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_trash_empty 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_trash_empty. 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_trash_empty 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