Delete a file (moves to trash by default)
AI agents call delete_file to permanently remove resources in Mail Cal Drive — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Although the file moves to trash rather than being permanently purged, deletion is still an irreversible user-facing action that destroys access to data. An AI agent with this capability could accidentally or maliciously delete important files across Microsoft 365, Google Workspace, or IMAP storage. This is destructive rather than merely Write because it removes data rather than creating or modifying it reversibly.
From the tool's definition Tool name is 'delete_file' and description states 'Delete a file (moves to trash by default)'. The action removes file data from the user's cloud storage or file system.
Attacks that exploit this kind of access
Delete a file (moves to trash by default). It is categorised as a Destructive tool in the Mail Cal Drive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mail Cal Drive MCP server in PolicyLayer and add a rule for delete_file: 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 Mail Cal Drive. Nothing to install.
delete_file 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 delete_file 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 delete_file. 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.
delete_file is provided by the Mail Cal Drive MCP server (rumbitopi/mail-cal-drive-mcp). 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 →