Create a new task in Dida365 with specified details including title, project ID, content, due date and priority. The task will be created under the specified project. Requires at least title and projectId. Returns the created task details.
AI agents use create_task to create or update resources in TickTick/Dida365 MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TickTick/Dida365 MCP Server environment.
The tool creates new task objects within a project, which is a reversible write operation. It does not execute arbitrary code, delete data, move money, or trigger external side effects beyond the creation of the task record itself. The blast radius is minimal—an erroneous task creation can be deleted or ignored.
From the tool's definition Tool description explicitly states 'Create a new task' and 'The task will be created under the specified project.' This is a create operation that adds new data to the system.
Documented attack patterns abuse exactly the kind of access create_task gives an agent:
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 create_task:
{
"version": "1",
"default": "deny",
"tools": {
"create_task": {
"limits": [
{
"counter": "create_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new task in Dida365 with specified details including title, project ID, content, due date and priority. The task will be created under the specified project. Requires at least title and projectId. Returns the created task details. It is categorised as a Write tool in the TickTick/Dida365 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TickTick/Dida365 MCP Server MCP server in PolicyLayer and add a rule for create_task: 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.
create_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_task 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 create_task. 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.
create_task 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.
Deterministic rules across all 11 TickTick/Dida365 MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 TickTick/Dida365 MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.