Updates multiple tasks in TickTick with new attributes in a single API call. This batch operation is more efficient than updating tasks individually. You must provide an array of tasks, where each task must include both the task ID and project ID. Each task can have different update parameters. R...
AI agents use batch-update-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.
This tool creates or modifies data reversibly, which is the definition of Write category. While it operates on multiple tasks (batch operation), the changes are not destructive or irreversible - attributes can be changed back. Severity is medium because a compromised agent could modify many tasks at once, but the impact is limited to task metadata/attributes rather than deletion or financial consequences.
From the tool's definition Tool description states it 'Updates multiple tasks in TickTick with new attributes' - the word 'Updates' indicates modification of existing data.
Documented attack patterns abuse exactly the kind of access batch-update-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-update-tasks:
{
"version": "1",
"default": "deny",
"tools": {
"batch-update-tasks": {
"limits": [
{
"counter": "batch-update-tasks_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch-update-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.
Updates multiple tasks in TickTick with new attributes in a single API call. This batch operation is more efficient than updating tasks individually. You must provide an array of tasks, where each task must include both the task ID and project ID. Each task can have different update parameters. Returns a summary of successful updates and any errors encountered. 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-update-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-update-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-update-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-update-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-update-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.