// SCAN REPORT

Dida365 Agent

44 tools. 29 can modify or destroy data without limits.

7 destructive tools with no built-in limits. Policy required.

Last updated: 30 Jun 2026

29 can modify or destroy data

15 read-only

44 tools total

Community server · catalogue entry verified 30/06/2026

How to control Dida365 Agent ↓

TOOL MAP

What Dida365 Agent exposes to your agents

Read (15) Write / Execute (22) Destructive / Financial (7)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Dida365 Agent tools

Destructive · High dida365_delete_habit Deletion of habits is an irreversible destructive action that cannot be undone. Destructive · High dida365_delete_tags This tool permanently removes tags from the task management system with no undo capability. Destructive · High dida365_delete_column This tool performs an irreversible deletion operation on a kanban column. Destructive · High dida365_delete_folder This tool performs an irreversible deletion operation.

29 of Dida365 Agent's 44 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Dida365 Agent

PolicyLayer is an MCP gateway — it sits between your AI agents and Dida365 Agent, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "dida365_delete_column": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "dida365_batch_complete_tasks": {
    "limits": [
      {
        "counter": "dida365_batch_complete_tasks_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "dida365_filter_tasks": {
    "limits": [
      {
        "counter": "dida365_filter_tasks_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Dida365 Agent — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON DIDA365 AGENT →

Instant setup, no code required.

FULL CATALOGUE

All 44 Dida365 Agent tools

DESTRUCTIVE 7 tools

Destructive dida365_delete_column Delete a kanban column. Tasks in it are not deleted. Destructive dida365_delete_folder Delete a project folder. Projects in the folder are not deleted. Destructive dida365_delete_habit Batch delete habits. Each dict should have "id". Destructive dida365_delete_project Permanently delete a project and all its tasks. This action cannot be undone. Destructive dida365_delete_tag Delete a single tag by name. Destructive dida365_delete_tags Batch delete tags. Each dict should have "name". Destructive dida365_delete_task Permanently delete a task. This action cannot be undone.

WRITE 22 tools

Write dida365_batch_complete_tasks Mark multiple tasks in a project as completed. Write dida365_batch_create_tasks Batch create multiple tasks in one request. Write dida365_batch_update_tasks Batch update multiple tasks in one request. Write dida365_checkin_habit dida365_checkin_habit Write dida365_complete_task Mark a task as completed. Write dida365_create_column Create a kanban column. Move tasks into it via update_task's columnId. Write dida365_create_folder Create a project folder. Write dida365_create_habit Batch create habits. Each dict should have "name" (required). Write dida365_create_project Create a project. view_mode: list|kanban|timeline. kind: TASK|NOTE. Write dida365_create_tags Batch create tags. Write dida365_create_task dida365_create_task Write dida365_move_task Move a task between projects. Write dida365_pin_task Pin or unpin a task. Write dida365_set_task_parent Set a task's parent to create a subtask relationship. Write dida365_undo_checkin Undo a habit checkin for a specific date. Write dida365_unset_task_parent Remove a task's parent, making it a top-level task. Write dida365_update_column Update a kanban column. Only provided fields are changed. Write dida365_update_folder Update a project folder. Only provided fields are changed. Write dida365_update_habit Batch update habits. Each dict should have "id" (required) plus fields to update. Write dida365_update_project Update a project. Only provided fields are changed. Write dida365_update_tags Batch update tags. Each dict should have "name" (required) plus fields to update. Write dida365_update_task dida365_update_task

READ 15 tools

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Dida365 Agent

Can an AI agent delete data through the Dida365 Agent MCP server? +

Yes. The Dida365 Agent server exposes 7 destructive tools including dida365_delete_column, dida365_delete_folder, dida365_delete_habit. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Dida365 Agent? +

The Dida365 Agent server has 22 write tools including dida365_batch_complete_tasks, dida365_batch_create_tasks, dida365_batch_update_tasks. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Dida365 Agent.

How many tools does the Dida365 Agent MCP server expose? +

44 tools across 3 categories: Destructive, Read, Write. 15 are read-only. 29 can modify, create, or delete data.

How do I enforce a policy on Dida365 Agent? +

Register the Dida365 Agent MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Dida365 Agent tool call.

Deterministic rules across all 44 Dida365 Agent tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DIDA365 AGENT →

Instant setup, no code required.

44 Dida365 Agent tools catalogued and risk-classified — across an index of 43,000+ MCP servers.