更新任务 (调用模块级逻辑函数) Args: task_id_or_title: 任务ID或任务标题 title: 新任务标题 content: 新任务内容 priority: 新优先级 (0-最低, 1-低, 3-中, 5-高) project_name: 新项目名称 tag_names: 新标签名称列表 start_date: 新开始日期，格式 'YYYY-MM-DD HH:MM:SS'，会自动转换为API所需的时区和格式 due_date: 新截止日期，格式 'YYYY-MM-DD HH:MM:SS'，会自动转换为API所需的时区和格式 is_all_day: 是否为全天任务 re...
AI agents use update_task to create or update resources in TickTick MCP Service — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TickTick MCP Service environment.
This tool creates or modifies data reversibly within the TickTick task management system. While it can change multiple task attributes, the modifications are not irreversible (tasks can be updated again or reverted), and no data is deleted or destroyed.
From the tool's definition Tool description states it updates task properties including title, content, priority, project, tags, dates, reminders, and status. The function modifies existing data (task fields) reversibly without deleting or executing external code.
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 MCP Service, 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.
更新任务 (调用模块级逻辑函数) Args: task_id_or_title: 任务ID或任务标题 title: 新任务标题 content: 新任务内容 priority: 新优先级 (0-最低, 1-低, 3-中, 5-高) project_name: 新项目名称 tag_names: 新标签名称列表 start_date: 新开始日期，格式 'YYYY-MM-DD HH:MM:SS'，会自动转换为API所需的时区和格式 due_date: 新截止日期，格式 'YYYY-MM-DD HH:MM:SS'，会自动转换为API所需的时区和格式 is_all_day: 是否为全天任务 reminder: 新提醒选项 status: 新状态，0表示未完成，2表示已完成 Returns: 更新后的任务信息. It is categorised as a Write tool in the TickTick MCP Service MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TickTick MCP Service 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 MCP Service. 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 Service MCP server (galaxyxieyu/didatodolist-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TickTick MCP Service, 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.
28 TickTick MCP Service tools catalogued and risk-classified — across an index of 43,000+ MCP servers.