AI agents use create_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.
The 'create_tag' tool creates and stores new tag data in a task management system, which is a reversible modification (tags can be deleted via sibling tool 'delete_tag'). This is a Write operation. Severity is medium because unauthorized tag creation could pollute the task management system and complicate data organization, but the impact is confined to metadata and is easily reversible.
From the tool's definition Tool is named 'create_tag' with no description provided. Based on the naming convention and context of sibling tools (create_task, create_project, create_goal), this tool creates new data in the TickTick system.
Documented attack patterns abuse exactly the kind of access create_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 create_tag:
{
"version": "1",
"default": "deny",
"tools": {
"create_tag": {
"limits": [
{
"counter": "create_tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
create_tag. 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 create_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.
create_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 create_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 create_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.
create_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.