Delete a file or folder from a project by its project-relative path. Maps to DELETE /projects/{projectId}/files/{path}. The backend auto-cleans dangling references to the deleted resource from the project configuration. Like writes, the deletion is staged in the working copy — commit it with open...
AI agents call delete_project_file to permanently remove resources in Openl — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes files or folders from a project with automatic cleanup of references. Although the deletion is staged (requiring commit via openl_save_project), it is inherently destructive and cannot be undone. The high severity reflects the risk of accidental or malicious data loss when an AI agent operates this tool without proper safeguards.
From the tool's definition Tool name contains 'delete', description explicitly states 'Delete a file or folder from a project' and 'The backend auto-cleans dangling references to the deleted resource'. The operation is irreversible and mapped to DELETE HTTP method.
Attacks that exploit this kind of access
Delete a file or folder from a project by its project-relative path. Maps to DELETE /projects/{projectId}/files/{path}. The backend auto-cleans dangling references to the deleted resource from the project configuration. Like writes, the deletion is staged in the working copy — commit it with openl_save_project. Use. It is categorised as a Destructive tool in the Openl MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Openl MCP server in PolicyLayer and add a rule for delete_project_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 Openl. Nothing to install.
delete_project_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_project_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_project_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_project_file is provided by the Openl MCP server (openl-mcp-server). 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 →