add_task
AI agents use add_task 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 new tasks represents a reversible write operation that modifies the user's task database. The blast radius is medium: an agent could add many unwanted tasks, but this can be undone by deletion. It does not move money (not Financial), delete data (not Destructive), or execute arbitrary code (not Execute). The empty description lowers confidence slightly from high to medium-high.
From the tool's definition Tool named 'add_task' is listed as a sibling alongside create_project, which demonstrates it creates new data entries. The server description confirms it supports 'task creation with priorities, due dates, recurring schedules.'
Attacks that exploit this kind of access
add_task. 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 add_task: 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.
add_task 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 add_task 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 add_task. 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.
add_task is provided by the TickTick MCP Server MCP server (kbadinger/ticktickmcp). 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 →