更新标签信息 Args: tag_id_or_name: 标签ID或标签名称 name: 新标签名称 color: 新标签颜色 Returns: 更新后的标签信息
AI agents use update_tag 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 modifies data reversibly by updating tag attributes. It is not a Read operation (it changes state), not Execute (it doesn't run arbitrary code or external operations), not Destructive (the tag itself persists and the change is reversible), and not Financial.
From the tool's definition Tool name 'update_tag' with description stating it updates tag information (更新标签信息); it modifies existing tag data by allowing changes to name and color properties via the 'name' and 'color' parameters.
Documented attack patterns abuse exactly the kind of access update_tag 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_tag:
{
"version": "1",
"default": "deny",
"tools": {
"update_tag": {
"limits": [
{
"counter": "update_tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_tag 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: tag_id_or_name: 标签ID或标签名称 name: 新标签名称 color: 新标签颜色 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_tag: 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_tag 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_tag 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_tag. 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_tag 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.