Delete a single file (not directories) if it exists and is mutable. Updates quota usage automatically.
AI agents call delete_file to permanently remove resources in MCP Files — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes files from the filesystem. Even though it operates within a constrained environment with access controls, deletion cannot be undone and represents data loss. An AI agent with access to this tool could maliciously or accidentally delete important project files, configuration files, or user data.
From the tool's definition Tool name is 'delete_file' and description states it will 'Delete a single file (not directories) if it exists and is mutable.' The word 'delete' combined with the permanent removal of files indicates an irreversible action.
Attacks that exploit this kind of access
Delete a single file (not directories) if it exists and is mutable. Updates quota usage automatically. It is categorised as a Destructive tool in the MCP Files MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Files 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 MCP Files. 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 MCP Files MCP server (tspspi/mcpfiles). 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 →