Create a new task in TickTick. Args: title: Task title project_id: ID of the project to add the task to content: Task description/content (optional) start_date: Start date in ISO format YYYY-MM-DDThh:mm:ss+0000 (optional) due_date: Due date in ISO format YYYY-MM-DDThh:mm:ss+0000 (optional) priori...
AI agents use create_task to create or update resources in Ticktick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ticktick environment.
This tool creates new task records in a task management system. Creation of data is a Write operation—it modifies state but is reversible (tasks can be deleted). It does not execute arbitrary code, delete data irreversibly, move money, or query sensitive information. The blast radius is minimal as accidental task creation causes no harm and can be easily undone.
From the tool's definition Tool description states 'Create a new task in TickTick' and accepts parameters for task creation (title, project_id, content, dates, priority). The action creates new data reversibly.
Documented attack patterns abuse exactly the kind of access create_task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ticktick, and nothing reaches the server without passing your rules. This is the rule we recommend for create_task:
{
"version": "1",
"default": "deny",
"tools": {
"create_task": {
"limits": [
{
"counter": "create_task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_task 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 a new task in TickTick. Args: title: Task title project_id: ID of the project to add the task to content: Task description/content (optional) start_date: Start date in ISO format YYYY-MM-DDThh:mm:ss+0000 (optional) due_date: Due date in ISO format YYYY-MM-DDThh:mm:ss+0000 (optional) priority: Priority level (0: None, 1: Low, 3: Medium, 5: High) (optional). It is categorised as a Write tool in the Ticktick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ticktick MCP server in PolicyLayer and add a rule for create_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. Nothing to install.
create_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 create_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 create_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.
create_task is provided by the Ticktick MCP server (jacepark12/ticktick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ticktick, 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.
22 Ticktick tools catalogued and risk-classified — across an index of 43,000+ MCP servers.