This record as markdown: /tools/ai-dataecho-mcp/drive-delete-file.md
What drive_delete_file does on Mcp
AI agents call drive_delete_file to permanently remove resources in Mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | File path |
drive | string | Yes | Drive name or drv_… id |
Parameters from the server's own tool schema.
Why drive_delete_file is rated Critical
This tool permanently removes files from persistent storage (a drive used for agent memory). File deletion is irreversible and represents data loss. While the blast radius is limited to a single file per invocation, the destructive nature and potential impact on agent memory/state systems justifies 'high' severity.
From the tool's definition Tool name: 'drive_delete_file'. Description: 'Delete one file from a drive.' The verb 'delete' combined with file removal is a destructive operation that cannot be undone.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs drive_delete_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drive_delete_file, this is the rule to start with:
drive_delete_file 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 Mcp, apply this rule, and every drive_delete_file call is checked against it from then on.
Questions about drive_delete_file
Delete one file from a drive. It is categorised as a Destructive tool in the Mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
drive_delete_file accepts 2 parameters: path, drive. Required: path, drive. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for drive_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 Mcp. Nothing to install.
drive_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 drive_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 drive_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.
drive_delete_file is provided by the MCP server (https://dataecho.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue