Create a subtask for a parent task within the same project. Args: subtask_title: Title of the subtask parent_task_id: ID of the parent task project_id: ID of the project (must be same for both parent and subtask) content: Optional content/description for the subtask priority: Priority level (0: N...
AI agents use create_subtask 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 data (a subtask) in TickTick but does not delete, execute arbitrary code, move money, or irreversibly modify existing data. The sibling tools include delete_task and delete_project which are more severe (Destructive).
From the tool's definition Tool creates a new subtask within a task management system. The description explicitly states 'Create a subtask' with parameters for title, parent task ID, project ID, content, and priority. This is a reversible data creation operation.
Documented attack patterns abuse exactly the kind of access create_subtask 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_subtask:
{
"version": "1",
"default": "deny",
"tools": {
"create_subtask": {
"limits": [
{
"counter": "create_subtask_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_subtask 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 subtask for a parent task within the same project. Args: subtask_title: Title of the subtask parent_task_id: ID of the parent task project_id: ID of the project (must be same for both parent and subtask) content: Optional content/description for the subtask 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_subtask: 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_subtask 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_subtask 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_subtask. 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_subtask 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.