Delete a project and all its associated tasks and subtasks. This action cannot be undone.
AI agents call delete_project to permanently remove resources in Agentic Tools MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data at scale—an entire project plus all dependent tasks and subtasks. The description explicitly confirms the action cannot be reversed, placing it unambiguously in the Destructive category. An AI agent invoking this without proper safeguards could erase substantial work product.
From the tool's definition Tool description explicitly states: 'Delete a project and all its associated tasks and subtasks. This action cannot be undone.' The use of 'delete' combined with 'cannot be undone' and cascade deletion of related data (tasks, subtasks) are definitive…
Documented attack patterns abuse exactly the kind of access delete_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agentic Tools MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_project:
{
"version": "1",
"default": "deny",
"hide": [
"delete_project"
]
} delete_project 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.
Delete a project and all its associated tasks and subtasks. This action cannot be undone. It is categorised as a Destructive tool in the Agentic Tools MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agentic Tools MCP Server MCP server in PolicyLayer and add a rule for delete_project: 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 Agentic Tools MCP Server. Nothing to install.
delete_project 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 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. 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 is provided by the Agentic Tools MCP Server MCP server (pimzino/agentic-tools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Agentic Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
29 Agentic Tools MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.