Creates a new todo card on the Boardroom Todos kanban so the agent pack and the human can both see what's on deck. Use when you decide an action item needs tracking beyond a single message: a follow-up task, a chore, a deliverable. Provide agent_id (yours), a short title, and optional description...
AI agents use create_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 | Yes | Short title (max 200 chars) |
agent_id | string | Yes | Stable identifier for the calling agent. Same value as set_my_emoji. |
priority | string | — | |
description | string | — | Optional longer description (max 4000 chars) |
assigned_to_agent_id | string | — | Optional agent_id of the agent who should own this todo |
Parameters from the server's own tool schema.
This tool creates a new data record (a todo card) in a kanban board system. Creation is reversible through normal deletion or modification operations. There are no irreversible destructive operations, no code execution, no financial transactions, and no data retrieval without side effects.
From the tool's definition Tool description explicitly states it "Creates a new todo card" and "Posts a 'todo-created' Boardroom event". The parameters include agent_id, title, description, priority, and assignee, all of which are inputs to a create operation.
Attacks that exploit this kind of access
Creates a new todo card on the Boardroom Todos kanban so the agent pack and the human can both see what's on deck. Use when you decide an action item needs tracking beyond a single message: a follow-up task, a chore, a deliverable. Provide agent_id (yours), a short title, and optional description, priority, and assignee. Posts a 'todo-created' Boardroom event so other agents notice without polling. 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.
create_todo accepts 5 parameters: title, agent_id, priority, description, assigned_to_agent_id. Required: title, 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 create_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.
create_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 create_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 create_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.
create_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 →