delete-project

THE RISK

Critical Risk

Why delete-project needs a policy

Deleting a project is a destructive operation that cannot be undone and will remove the project and potentially associated tasks or metadata. While the blast radius is limited to a single project (not system-wide), the irreversible nature of data deletion warrants the Destructive category and high severity. Confidence is high because the intent is explicit and unambiguous.

From the tool's definition Tool name is 'delete-project' and description states 'Delete a project'. The verb 'delete' indicates irreversible removal of data.

Documented attack patterns abuse exactly the kind of access delete-project gives an agent:

POLICY

How to control delete-project

PolicyLayer is an MCP gateway — it sits between your AI agents and Dida, and nothing reaches the server without passing your rules. This is the rule we recommend for delete-project:

policy.json

{
  "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.

Create a free account and register Dida — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Dida tools

Destructive batch-delete-tasks Permanently removes multiple tasks from TickTick in a single operation. This batch operati Destructive complete-task Marks a task as completed in TickTick. This tool automatically finds the project containin Destructive delete-task Permanently removes a task from TickTick. You must provide both the task ID and the projec Write batch-move-tasks Moves multiple tasks between projects in a single operation. This batch operation is more Write batch-update-tasks Updates multiple tasks in TickTick with new attributes in a single API call. This batch op Write create-project Create a new project Write create-task Creates a new task in TickTick with specified attributes. You can set title, content, prio Write move-task Moves a task from one project to another in TickTick. You must specify the task ID, source

All 18 Dida tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Dida → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete-project

What does the delete-project tool do? +

Delete a project. It is categorised as a Destructive tool in the Dida MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete-project? +

Register the Dida 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 Dida. Nothing to install.

What risk level is delete-project? +

delete-project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-project? +

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.

How do I block delete-project completely? +

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.

What MCP server provides delete-project? +

delete-project is provided by the Dida MCP server (zhongwencool/dida-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dida tool call.

Start from Dida, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →