DESTRUCTIVE. Permanently delete a TRASHED file. Bypasses the trash safety net. Requires drive:*:purge scope AND TREKMAIL_ALLOW_DESTRUCTIVE=true.
AI agents call drive_file_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.
This tool permanently deletes files without recovery options, irreversibly destroying data. It requires explicit destructive authorization and bypasses safety mechanisms (trash). The blast radius is critical—an AI agent misusing this could permanently lose important files for users. This is unambiguously a Destructive action (not merely Write), making it the highest severity risk.
From the tool's definition Tool description explicitly states 'DESTRUCTIVE. Permanently delete a TRASHED file. Bypasses the trash safety net.' The name 'drive_file_purge' also indicates irreversible deletion.
Attacks that exploit this kind of access
DESTRUCTIVE. Permanently delete a TRASHED file. Bypasses the trash safety net. 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_file_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_file_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_file_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_file_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_file_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →