Updates an existing task in TickTick with new attributes. You must provide both the task ID and the project ID. You can modify any combination of title, content, priority, due date, start date, all-day status, and tags. Only the specified fields will be updated; others remain unchanged. Tags shou...
AI agents use update-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.
The tool modifies task attributes (title, content, priority, due date, start date, all-day status, tags) in a reversible manner. While it changes data, these modifications can be undone by subsequent updates, distinguishing it from Destructive operations. It does not delete data, execute arbitrary code, or involve financial transactions.
From the tool's definition Tool description states 'Updates an existing task' and 'Only the specified fields will be updated; others remain unchanged.' This is a reversible modification operation that creates or modifies data without deleting it.
Documented attack patterns abuse exactly the kind of access update-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 update-task:
{
"version": "1",
"default": "deny",
"tools": {
"update-task": {
"limits": [
{
"counter": "update-task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-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.
Updates an existing task in TickTick with new attributes. You must provide both the task ID and the project ID. You can modify any combination of title, content, priority, due date, start date, all-day status, and tags. Only the specified fields will be updated; others remain unchanged. Tags should be provided as a comma-separated list without # symbols. Returns the updated task with all its current attributes. 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 update-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.
update-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 update-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 update-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.
update-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.