create_task
AI agents use create_task to create or update resources in Todoist MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP Server environment.
This tool creates new tasks in Todoist, which modifies the user's task list reversibly. Creating a task is a Write operation—it adds data that can be edited or deleted later. Severity is medium because an AI agent misusing this could create many unwanted tasks, cluttering the user's Todoist, but the impact is reversible and confined to task management rather than financial or destructive operations.
From the tool's definition The tool name is 'create_task' and the server description states it 'enables AI agents to create and list tasks in Todoist using natural language.' The action of creating tasks is explicitly stated as a core capability.
Attacks that exploit this kind of access
create_task. It is categorised as a Write tool in the Todoist MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP Server 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 Todoist MCP Server. 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 Todoist MCP Server MCP server (mehularora8/todoist-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 →