drive_bulk_purge

DESTRUCTIVE. Hard-delete N TRASHED items. Items not currently in trash are silently skipped. Requires drive:*:purge scope AND TREKMAIL_ALLOW_DESTRUCTIVE=true.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/drive-bulk-purge.md

WHAT IT DOES

What drive_bulk_purge does on TrekMail MCP Server

AI agents call drive_bulk_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.

RISK

Why drive_bulk_purge is rated Critical

This tool permanently and irreversibly deletes multiple items from a user's drive. The hard-delete operation cannot be undone, and the requirement for an explicit destructive-mode flag indicates the developers recognized this as a high-risk operation. The ability to delete N items in bulk amplifies the blast radius. This is a clear Destructive category tool with critical severity due to data loss potential.

From the tool's definition Tool name contains 'purge'; description explicitly states 'DESTRUCTIVE. Hard-delete N TRASHED items.' and requires 'TREKMAIL_ALLOW_DESTRUCTIVE=true' flag.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs drive_bulk_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_bulk_purge, this is the rule to start with:

drive_bulk_purge Hidden

drive_bulk_purge is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "drive_bulk_purge"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every drive_bulk_purge call is checked against it from then on.

FAQ

Questions about drive_bulk_purge

What does the drive_bulk_purge tool do? +

DESTRUCTIVE. Hard-delete N TRASHED items. Items not currently in trash are silently skipped. 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.

How do I enforce a policy on drive_bulk_purge? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_bulk_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.

What risk level is drive_bulk_purge? +

drive_bulk_purge is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit drive_bulk_purge? +

Yes. Add a rate_limit block to the drive_bulk_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.

How do I block drive_bulk_purge completely? +

Set action: deny in the PolicyLayer policy for drive_bulk_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.

What MCP server provides drive_bulk_purge? +

drive_bulk_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.

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 248 TrekMail MCP Server tools → Critical-risk tools on this server →

Across the catalogue

archive_purge on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →