This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/todoist-create-task.md
What todoist_create_task does on UnClick
AI agents use todoist_create_task to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
content | string | Yes | The task text |
priority | number | — | Priority 1 (normal) to 4 (urgent) |
api_token | string | Yes | Todoist API token |
due_string | string | — | Natural-language due date (e.g. 'tomorrow 5pm') |
project_id | string | — | Project id to add the task to |
Parameters from the server's own tool schema.
Why todoist_create_task is rated Medium
Creating a task is a write operation that adds data to a user's task list. It is reversible (tasks can be deleted), so it does not qualify as Destructive. The impact is limited to task data within a single application with low blast radius if misused by an AI agent (at worst, creating unwanted tasks that clutter a user's todo list).
From the tool's definition Tool name contains 'create' and description states 'Create a Todoist task.' This creates new data in the Todoist task management system.
Risk signalsAccepts raw HTML/template content (content)
Attacks that exploit this kind of access
The rule that runs todoist_create_task safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For todoist_create_task, this is the rule to start with:
todoist_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.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every todoist_create_task call is checked against it from then on.
Questions about todoist_create_task
Create a Todoist task. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
todoist_create_task accepts 5 parameters: content, priority, api_token, due_string, project_id. Required: content, api_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for todoist_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 UnClick. Nothing to install.
todoist_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 todoist_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 todoist_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.
todoist_create_task is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue