Deletes a named file from the project
AI agents call delete_project_file to permanently remove resources in Task Trellis MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes data (project files) and cannot be undone. Deletion operations fall squarely into the Destructive category. The severity is high because an AI agent with misguided instructions could delete critical project files, causing loss of work and project damage. Confidence is very high due to the explicit use of 'delete' in both name and description.
From the tool's definition Tool name is 'delete_project_file' and description states it 'Deletes a named file from the project'. The verb 'Deletes' is explicit and unambiguous.
Documented attack patterns abuse exactly the kind of access delete_project_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Task Trellis MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_project_file:
{
"version": "1",
"default": "deny",
"hide": [
"delete_project_file"
]
} delete_project_file disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Deletes a named file from the project. It is categorised as a Destructive tool in the Task Trellis MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Task Trellis 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 Task Trellis MCP. 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 Task Trellis MCP server (langadventurellc/task-trellis-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Task Trellis MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 Task Trellis MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.