batch_create_tasks
AI agents use batch_create_tasks to create or update resources in Ticktick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ticktick environment.
This tool creates (writes) task records in batch, which is reversible via delete operations. The batch nature increases severity from low to medium due to potential for bulk unintended task creation, but remains Write rather than Execute since it performs a standard data creation operation rather than executing arbitrary code.
From the tool's definition Tool name 'batch_create_tasks' indicates creation of multiple task records. Description is empty, but sibling tools like 'create_task' and 'create_subtask' establish the pattern of write operations on the TickTick task management system.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access batch_create_tasks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ticktick, and nothing reaches the server without passing your rules. This is the rule we recommend for batch_create_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"batch_create_tasks": {
"limits": [
{
"counter": "batch_create_tasks_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}batch_create_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.
batch_create_tasks. It is categorised as a Write tool in the Ticktick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ticktick MCP server in PolicyLayer and add a rule for batch_create_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 Ticktick. Nothing to install.
batch_create_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_create_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_create_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_create_tasks is provided by the Ticktick MCP server (jacepark12/ticktick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ticktick, 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.
22 Ticktick tools catalogued and risk-classified — across an index of 43,000+ MCP servers.