Creates a new task in TickTick with specified attributes. You can set title, content, priority (0-5), due date, project, and tags. If no project is specified, the task will be created in the Inbox. Tags should be provided as a comma-separated list without # symbols. Returns the created task detai...
AI agents use create-task to create or update resources in Dida — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dida environment.
This tool creates new tasks in a task management system, which is a reversible write operation. Tasks can be deleted or modified later, so this does not fall into Destructive category. It does not execute arbitrary code, trigger external operations based on dynamic arguments, move money, or retrieve data without modification. The blast radius of misuse is limited to creating unwanted tasks, which is low severity.
From the tool's definition Tool description explicitly states it 'Creates a new task in TickTick with specified attributes' and 'Returns the created task details including its assigned ID.' The action is creating and modifying task data reversibly.
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 Dida, 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.
Creates a new task in TickTick with specified attributes. You can set title, content, priority (0-5), due date, project, and tags. If no project is specified, the task will be created in the Inbox. Tags should be provided as a comma-separated list without # symbols. Returns the created task details including its assigned ID. It is categorised as a Write tool in the Dida MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dida 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 Dida. 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 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.
Start from Dida, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Dida tools catalogued and risk-classified — across an index of 43,000+ MCP servers.