Permanently delete a file. Will not delete directories. Use with caution as this operation cannot be undone. Only works within allowed directories.
AI agents call delete_file to permanently remove resources in FilesystemMCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes files with no recovery mechanism. Although it is scoped to allowed directories, the permanent deletion of data constitutes a destructive action with significant blast radius if an AI agent misuses it by deleting critical files. Destructive is the most severe applicable category and takes precedence over Write.
From the tool's definition Tool description explicitly states 'Permanently delete a file' and 'this operation cannot be undone.' The name 'delete_file' combined with the irreversible nature of the action clearly indicates destructive capability.
Attacks that exploit this kind of access
Permanently delete a file. Will not delete directories. Use with caution as this operation cannot be undone. Only works within allowed directories. It is categorised as a Destructive tool in the FilesystemMCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Filesystem 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 FilesystemMCP. 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 Filesystem MCP server (rijadalisic/filesystemmcp). 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 →