Update an existing task in TickTick. Args: task_id: ID of the task to update project_id: ID of the project the task belongs to title: New task title (optional) content: New task description/content (optional) start_date: New start date in ISO format YYYY-MM-DDThh:mm:ss+0000 (optional) due_date: N...
AI agents use update_task 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 or modifies data in a reversible manner without deleting information, triggering external operations, moving money, or executing arbitrary code. It fits the Write category: users can update task details and those changes can be undone by updating again. Severity is low because task management updates have limited blast radius and no cascading destructive effects.
From the tool's definition Tool description states 'Update an existing task in TickTick' with optional parameters for modifying task properties (title, content, start_date, due_date, priority). The function is reversible—updates can be changed by subsequent calls.
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 Ticktick, 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.
Update an existing task in TickTick. Args: task_id: ID of the task to update project_id: ID of the project the task belongs to title: New task title (optional) content: New task description/content (optional) start_date: New start date in ISO format YYYY-MM-DDThh:mm:ss+0000 (optional) due_date: New due date in ISO format YYYY-MM-DDThh:mm:ss+0000 (optional) priority: New priority level (0: None, 1: Low, 3: Medium, 5: High) (optional). 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 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 Ticktick. 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 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.