重命名标签 Args: old_name: 旧标签名称 new_name: 新标签名称 Returns: 操作响应
AI agents use rename_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 existing data (tag names) in a reversible manner. It does not delete, execute code, move money, or query data without side effects. The blast radius is minimal since renaming a tag affects only that tag's metadata and dependent references, with no destructive or irreversible consequences. Categorized as Write rather than Read (which has no side effects) or Destructive (which is irreversible).
From the tool's definition Tool renames an existing tag by modifying its name from old_name to new_name. The operation is reversible (a tag can be renamed back), and the description indicates it's a modification operation ("重命名标签" = "rename tag").
Documented attack patterns abuse exactly the kind of access rename_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 rename_tag:
{
"version": "1",
"default": "deny",
"tools": {
"rename_tag": {
"limits": [
{
"counter": "rename_tag_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}rename_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: old_name: 旧标签名称 new_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 rename_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.
rename_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 rename_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 rename_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.
rename_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.