Update a todo's title, description, priority, status, or assignee. Use when scope changes, ownership shifts, or you move it between kanban columns ('open', 'in_progress', 'done', 'dropped'). agent_id required for attribution.
AI agents use update_todo 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 |
|---|---|---|---|
title | string | — | |
status | string | — | |
todo_id | string | Yes | UUID of the todo to update |
agent_id | string | Yes | Stable identifier for the calling agent. |
priority | string | — | |
description | string | — | |
assigned_to_agent_id | string | — | Pass empty string to unassign |
Parameters from the server's own tool schema.
The tool creates or modifies data (todo items) in a reversible manner without deleting or destroying records. The updates to title, description, priority, status, and assignee are typical Write operations. Severity is medium because misuse could result in task data corruption or workflow disruption, but changes can be reverted. The required agent_id parameter provides some auditability.
From the tool's definition Tool description explicitly states 'Update a todo's title, description, priority, status, or assignee' and references moving items 'between kanban columns'. These are reversible modifications to data state.
Attacks that exploit this kind of access
Update a todo's title, description, priority, status, or assignee. Use when scope changes, ownership shifts, or you move it between kanban columns ('open', 'in_progress', 'done', 'dropped'). agent_id required for attribution. 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.
update_todo accepts 7 parameters: title, status, todo_id, agent_id, priority, description, assigned_to_agent_id. Required: todo_id, agent_id. 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 update_todo: 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.
update_todo 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_todo 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_todo. 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_todo 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.
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 →