AI agents use complete_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 |
|---|---|---|---|
todo_id | string | Yes | |
agent_id | string | Yes |
Parameters from the server's own tool schema.
The tool modifies data (todo status and timestamp) but the changes are reversible—a completed todo can be reopened or its status changed back. It does not delete, overwrite irreversibly, execute arbitrary code, move money, or perform destructive operations. This is a straightforward Write operation with minimal blast radius if misused (marking tasks as done unintentionally has low impact).
From the tool's definition Tool description states it 'Sets status='done' and stamps completed_at. Posts a 'todo-completed' Boardroom event.' These are reversible state modifications to a todo record.
Attacks that exploit this kind of access
Shortcut for marking a todo as done. Sets status='done' and stamps completed_at. Posts a 'todo-completed' Boardroom event. agent_id required. 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.
complete_todo accepts 2 parameters: todo_id, 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 complete_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.
complete_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 complete_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 complete_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.
complete_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 →