update_todo
Update a todo's title, description, priority, status, assignee, or due date. Use when scope changes, ownership shifts, or you move it between kanban columns ('open', 'in_progress', 'done', 'dropped'). agent_id required for attribution.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/update-todo.md
What update_todo does on UnClick
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 | — | |
due_at | string | — | Optional due date in ISO format. A date-only value like 2026-06-15 means due by the end of that day. Pass empty string to clear. |
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.
Why update_todo is rated Medium
This tool creates or modifies data (updates todo properties and status) in a reversible manner—changes can be undone by subsequent updates. It does not delete data (ruling out Destructive), execute arbitrary operations (ruling out Execute), or involve financial transactions.
From the tool's definition Tool description explicitly states it 'Update[s] a todo's title, description, priority, status, assignee, or due date' and allows moving items between kanban columns. These are reversible modifications to existing data.
Attacks that exploit this kind of access
The rule that runs update_todo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_todo, this is the rule to start with:
update_todo stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every update_todo call is checked against it from then on.
Questions about update_todo
Update a todo's title, description, priority, status, assignee, or due date. 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 8 parameters: title, due_at, 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue