Moves multiple tasks between projects in a single operation. This batch operation is more efficient than moving tasks individually. You must provide an array of moves, where each move must include the task ID, source project ID, and destination project ID. This operation preserves all task attrib...
AI agents use batch-move-tasks 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.
Batch-move-tasks modifies task state (project assignments) reversibly. While the batch operation affects multiple records, the changes are not destructive (tasks and data remain intact) and do not execute external code or trigger financial transactions. This qualifies as Write — a create/update/modify operation.
From the tool's definition Tool performs 'Moves multiple tasks between projects' and 'preserves all task attributes while changing only their project associations' — a reversible modification of task metadata (project association).
Documented attack patterns abuse exactly the kind of access batch-move-tasks 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 batch-move-tasks:
{
"version": "1",
"default": "deny",
"tools": {
"batch-move-tasks": {
"limits": [
{
"counter": "batch-move-tasks_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch-move-tasks 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 multiple tasks between projects in a single operation. This batch operation is more efficient than moving tasks individually. You must provide an array of moves, where each move must include the task ID, source project ID, and destination project ID. This operation preserves all task attributes while changing only their project associations. 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 batch-move-tasks: 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.
batch-move-tasks 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 batch-move-tasks 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 batch-move-tasks. 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.
batch-move-tasks 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.