Moves a task from one project to another in TickTick. You must specify the task ID, source project ID, and destination project ID. This tool preserves all task attributes including title, content, due date, priority, and tags while changing only its project association. This operation requires v2...
AI agents use move-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 move-task tool modifies task state by changing a task's project association. This is a Write operation because it creates or modifies data reversibly—the task and all its attributes remain intact, and the operation can be undone by moving the task back to its original project. While it operates on user data, the blast radius is limited to task organization metadata rather than data destruction or code execution.
From the tool's definition Tool description states it 'Moves a task from one project to another' and 'preserves all task attributes while changing only its project association.' This is a reversible modification of task metadata (project association), not deletion or irreversible…
Documented attack patterns abuse exactly the kind of access move-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 move-task:
{
"version": "1",
"default": "deny",
"tools": {
"move-task": {
"limits": [
{
"counter": "move-task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move-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.
Moves a task from one project to another in TickTick. You must specify the task ID, source project ID, and destination project ID. This tool preserves all task attributes including title, content, due date, priority, and tags while changing only its project association. This operation requires v2 API authentication. 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 move-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.
move-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 move-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 move-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.
move-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.