Create a new tag.
AI agents use ticktick_create_tag 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.
Creating a tag is a reversible write operation that adds metadata to the TickTick system. Tags can be modified or deleted later, so this is not destructive. There is no code execution, financial transaction, or data retrieval involved. The blast radius is minimal—a mistaken tag creation has low impact and can be easily corrected.
From the tool's definition Tool name 'ticktick_create_tag' and description 'Create a new tag' indicate creation of new data without permanent deletion or external execution.
Attacks that exploit this kind of access
Create a new tag. 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_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 Server. Nothing to install.
ticktick_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 ticktick_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 ticktick_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.
ticktick_create_tag is provided by the TickTick MCP Server MCP server (mostafasuliman/ticktick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →