删除标签 Args: tag_id_or_name: 标签ID或标签名称 Returns: 删除操作的响应
AI agents call delete_tag to permanently remove resources in TickTick MCP Service — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes tags from the TickTick system. Deletion is irreversible and cannot be undone. While the blast radius is somewhat limited compared to deleting projects or tasks (which may affect more data), it still destroys data definitively. Destructive category is most appropriate as it matches the rule for irreversibly deleting data.
From the tool's definition Tool name is 'delete_tag' and description states '删除标签' (delete tag). The function takes 'tag_id_or_name' and returns deletion operation response, indicating irreversible removal of tag data.
Documented attack patterns abuse exactly the kind of access delete_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 delete_tag:
{
"version": "1",
"default": "deny",
"hide": [
"delete_tag"
]
}delete_tag disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
删除标签 Args: tag_id_or_name: 标签ID或标签名称 Returns: 删除操作的响应. It is categorised as a Destructive tool in the TickTick MCP Service MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TickTick MCP Service MCP server in PolicyLayer and add a rule for delete_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.
delete_tag is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.