updateTask
AI agents use updateTask 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 or modifies task data reversibly without permanently destroying information. While the description is empty, the name and sibling context make the intent clear. The severity is medium because unintended task modifications could cause user confusion or workflow disruption, but changes are reversible via re-editing or undo operations.
From the tool's definition Tool name 'updateTask' indicates modification of task data. The server context shows this is part of Todoist task management, alongside sibling tools like 'createTask', 'completeTask', and 'deleteProject'.
Attacks that exploit this kind of access
updateTask. 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 updateTask: 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.
updateTask 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 updateTask 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 updateTask. 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.
updateTask is provided by the Todoist MCP Server MCP server (stevengonsalvez/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 →