合并标签 Args: source_name: 源标签名称（将被合并的标签） target_name: 目标标签名称（合并到的标签） Returns: 操作响应
AI agents use merge_tags 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.
Merging tags is a data modification operation that reorganizes metadata. It is reversible (unlike deletion) and does not execute arbitrary code or move money. It ranks as Write rather than Destructive because the underlying data remains accessible under the target tag name, and the operation can be undone by re-splitting tags or restoring from backup.
From the tool's definition Tool merges tags by combining a source tag into a target tag. Description states '合并标签' (merge tags) with source_name and target_name parameters. This modifies tag organization but is reversible—tags can be unmerged or recreated.
Documented attack patterns abuse exactly the kind of access merge_tags 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 merge_tags:
{
"version": "1",
"default": "deny",
"tools": {
"merge_tags": {
"limits": [
{
"counter": "merge_tags_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}merge_tags 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: source_name: 源标签名称（将被合并的标签） target_name: 目标标签名称（合并到的标签） 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 merge_tags: 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.
merge_tags 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 merge_tags 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 merge_tags. 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.
merge_tags 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.