files.delete_file
Permanently delete a file from the authenticated account's upload storage. Pass file_name from files.list_uploaded_files. The file is removed from storage and any linked upload session is marked expired. Cost = 0 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/files.delete-file.md
What files.delete_file does on Vee3
AI agents call files.delete_file to permanently remove resources in Vee3, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
file_name | string | Yes | Relative file name or path to delete. Use files.list_uploaded_files to see available names. |
Parameters from the server's own tool schema.
Why files.delete_file is rated Critical
Tool irreversibly removes data; once deleted, files cannot be recovered from storage.
From the tool's definition Permanently delete a file from the authenticated account's upload storage.
Attacks that exploit this kind of access
The rule that runs files.delete_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For files.delete_file, this is the rule to start with:
files.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 Vee3, apply this rule, and every files.delete_file call is checked against it from then on.
Questions about files.delete_file
Permanently delete a file from the authenticated account's upload storage. Pass file_name from files.list_uploaded_files. The file is removed from storage and any linked upload session is marked expired. Cost = 0 tokens. It is categorised as a Destructive tool in the Vee3 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
files.delete_file accepts 1 parameter: file_name. Required: file_name. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for files.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 Vee3. Nothing to install.
files.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 files.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 files.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.
files.delete_file is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
Across the catalogue