更新目标 Args: goal_id: 目标ID (任务ID) title: 新标题 (可选) type: 新类型 (phase/permanent/habit) (可选) status: 新状态 (active/completed) (可选) keywords: 新关键词 (逗号分隔) (可选) description: 新的基础描述 (可选) due_date: 新截止日期 (YYYY-MM-DD) (可选) start_date: 新开始日期 (YYYY-MM-DD) (可选) frequency: 新频率 (可选) progress: 进度 (忽略) related_projec...
AI agents use update_goal 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 by updating goal attributes in the TickTick system. It does not delete data (which would be Destructive), does not execute arbitrary code (which would be Execute), and does not involve financial transactions (which would be Financial).
From the tool's definition Tool name 'update_goal' and description '更新目标' (update goal) with parameters that modify goal properties: title, type, status, keywords, description, due_date, start_date, frequency.
Documented attack patterns abuse exactly the kind of access update_goal 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_goal:
{
"version": "1",
"default": "deny",
"tools": {
"update_goal": {
"limits": [
{
"counter": "update_goal_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_goal 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: goal_id: 目标ID (任务ID) title: 新标题 (可选) type: 新类型 (phase/permanent/habit) (可选) status: 新状态 (active/completed) (可选) keywords: 新关键词 (逗号分隔) (可选) description: 新的基础描述 (可选) due_date: 新截止日期 (YYYY-MM-DD) (可选) start_date: 新开始日期 (YYYY-MM-DD) (可选) frequency: 新频率 (可选) progress: 进度 (忽略) related_projects: 相关项目 (忽略) 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_goal: 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_goal 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_goal 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_goal. 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_goal 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.