Delete a file or directory. Use with extreme caution as this operation cannot be undone. When deleting directories, all contents will be permanently removed. The recursive option must be explicitly set to true to delete non-empty directories. Only works within allowed directories.
AI agents call delete_file to permanently remove resources in Project Explorer MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes files and directories with no recovery mechanism. The irreversible nature of deletion and potential to remove multiple files recursively places it in the Destructive category. Severity is high rather than critical because the scope is limited to allowed directories (containment), but any misuse would result in permanent data loss within that scope.
From the tool's definition Tool description explicitly states 'Delete a file or directory' and 'this operation cannot be undone' and 'all contents will be permanently removed.' The warning 'Use with extreme caution' further confirms irreversible data loss.
Attacks that exploit this kind of access
Delete a file or directory. Use with extreme caution as this operation cannot be undone. When deleting directories, all contents will be permanently removed. The recursive option must be explicitly set to true to delete non-empty directories. Only works within allowed directories. It is categorised as a Destructive tool in the Project Explorer MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Project Explorer MCP Server 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 Project Explorer MCP Server. 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 Project Explorer MCP Server MCP server (mausrundung/mcp-explorer). 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 →