drive_bulk_trash
Soft-delete N items in one call. Caps at 5000 items per request.
This record as markdown: /tools/trekmail-mcp-server/drive-bulk-trash.md
What drive_bulk_trash does on TrekMail MCP Server
AI agents call drive_bulk_trash 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_bulk_trash is rated Critical
Although described as 'soft-delete' (potentially recoverable), the tool removes data from its normal state in the system at scale (up to 5000 items). This is an irreversible action from an end-user workflow perspective and carries high blast radius if invoked without authorization or with incorrect parameters. Soft-delete is still destructive in the context of an agent losing access to data.
From the tool's definition Tool is named 'drive_bulk_trash' and described as 'Soft-delete N items in one call. Caps at 5000 items per request.' The verb 'delete' and the action of moving items to trash (even if soft-delete) removes data from normal access and workflow; bulk deletion of…
Attacks that exploit this kind of access
The rule that runs drive_bulk_trash 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_bulk_trash, this is the rule to start with:
drive_bulk_trash 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_bulk_trash call is checked against it from then on.
Questions about drive_bulk_trash
Soft-delete N items in one call. Caps at 5000 items per request. 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_bulk_trash: 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_bulk_trash 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_bulk_trash 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_bulk_trash. 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_bulk_trash 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