Update a task in Todoist
AI agents use update-task to create or update resources in Todoist MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todoist MCP environment.
Updating a task is a write operation that modifies existing data in Todoist (task properties, content, assignments, dates, etc.). It is reversible — changes can be undone or modified again — distinguishing it from destructive operations. Severity is medium because task modifications could disrupt workflows or schedules if misapplied, but the impact is limited to task metadata and generally recoverable.
From the tool's definition Tool description states 'Update a task in Todoist' — a modification operation. Server context shows this is part of task management functionality alongside create (add-task), delete (delete-project), and read operations.
Attacks that exploit this kind of access
Update a task in Todoist. It is categorised as a Write tool in the Todoist MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todoist MCP server in PolicyLayer and add a rule for update-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. Nothing to install.
update-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 update-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 update-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.
update-task is provided by the Todoist MCP server (miottid/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 →