Create a new task in Todoist
AI agents use todoist_create_task to create or update resources in MCP Todoist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Todoist environment.
Creating a task is a Write operation: it adds new data to the system but does not irreversibly destroy data or execute arbitrary code. The blast radius is medium because an AI agent could spam task creation, cluttering a user's task list, but the impact is recoverable through deletion. No financial transactions or destructive operations are involved.
From the tool's definition Tool name 'todoist_create_task' and description 'Create a new task in Todoist' indicate data creation. This is a reversible operation—tasks can be deleted or modified later.
Attacks that exploit this kind of access
Create a new task in Todoist. It is categorised as a Write tool in the MCP Todoist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Todoist 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 MCP Todoist. 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 MCP Todoist MCP server (kentaroh7777/mcp-todoist). 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 →