AI agents use ticktick_merge_tags to create or update resources in TickTick MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TickTick MCP Server environment.
Merging tags modifies data structure and relationships within the task management system. It does not delete irreversibly (hence not Destructive), does not execute arbitrary code or trigger external operations (hence not Execute), and does not move money (hence not Financial). It is a data modification operation that creates or transforms existing data, fitting the Write category.
From the tool's definition Tool name 'ticktick_merge_tags' and description 'Merge two tags into one' indicates a modification operation that combines two existing tags.
Documented attack patterns abuse exactly the kind of access ticktick_merge_tags gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TickTick MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ticktick_merge_tags:
{
"version": "1",
"default": "deny",
"tools": {
"ticktick_merge_tags": {
"limits": [
{
"counter": "ticktick_merge_tags_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ticktick_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.
Merge two tags into one. It is categorised as a Write tool in the TickTick MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TickTick MCP Server MCP server in PolicyLayer and add a rule for ticktick_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 Server. Nothing to install.
ticktick_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 ticktick_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 ticktick_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.
ticktick_merge_tags is provided by the TickTick MCP Server MCP server (liadgez/ticktick-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TickTick MCP Server, 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.
114 TickTick MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.