delete_project_by_projectID

THE RISK

Critical Risk

This tool irreversibly removes data (a project and all associated tasks) and cannot be undone. Destructive is the primary category per the hierarchy. Severity is high because accidental use could result in loss of significant amounts of user data (entire projects and their tasks). Confidence is very high given the explicit 'Permanently delete' language and clear documentation of cascading deletions.

From the tool's definition "Permanently delete a project" and "will also delete all tasks within the project" indicate irreversible deletion of data with cascading effects.

Documented attack patterns abuse exactly the kind of access delete_project_by_projectID gives an agent:

HOW TO CONTROL DELETE_PROJECT_BY_PROJECTID

PolicyLayer is an MCP gateway — it sits between your AI agents and TickTick/Dida365 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_project_by_projectID:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_project_by_projectID"
  ]
}

delete_project_by_projectID 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 TickTick/Dida365 MCP Server — 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

More TickTick/Dida365 MCP Server tools

Destructive delete_task Permanently delete a task from a project. Requires both task ID and project ID for confirm Write complete_task Mark a task as completed. Requires both task ID and project ID. Updates the task Write create_project Create a new project in Dida365. Requires at least a project name. Can specify color, view Write create_task Create a new task in Dida365 with specified details including title, project ID, content, Write update_project_by_projectID Update an existing project Write update_task Modify an existing task Read get_project_by_projectId Get detailed information about a specific project by its ID. Returns project metadata incl Read get_projects Retrieve a list of all projects in the Dida365 account. Returns project details including

All 11 TickTick/Dida365 MCP Server tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in TickTick/Dida365 MCP Server → 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.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the delete_project_by_projectID tool do? +

Permanently delete a project by its ID. This will also delete all tasks within the project. Returns success message upon deletion. It is categorised as a Destructive tool in the TickTick/Dida365 MCP Server 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_by_projectID? +

Register the TickTick/Dida365 MCP Server MCP server in PolicyLayer and add a rule for delete_project_by_projectID: 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 TickTick/Dida365 MCP Server. Nothing to install.

What risk level is delete_project_by_projectID? +

delete_project_by_projectID 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_by_projectID? +

Yes. Add a rate_limit block to the delete_project_by_projectID 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_by_projectID completely? +

Set action: deny in the PolicyLayer policy for delete_project_by_projectID. 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_by_projectID? +

delete_project_by_projectID is provided by the TickTick/Dida365 MCP Server MCP server (zh1754629545/dida365-mcp-servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every TickTick/Dida365 MCP Server tool call.

Deterministic rules across all 11 TickTick/Dida365 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN TICKTICK/DIDA365 →

Free to start. No card required.

11 TickTick/Dida365 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

delete_project_by_projectID

// WHAT DELETE_PROJECT_BY_PROJECTID ON TICKTICK/DIDA365 MCP SERVER DOES

// THE RISK

// HOW TO CONTROL DELETE_PROJECT_BY_PROJECTID

// EXPLORE