list_todos
Returns todos for this tenant, optionally filtered by status. Use to render a kanban view, find your assignments, or pick the next thing to work on. agent_id required.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/list-todos.md
What list_todos does on UnClick
AI agents call list_todos to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
status | string | — | Optional filter |
agent_id | string | Yes | |
assigned_to_agent_id | string | — | Optional filter to a specific assignee |
Parameters from the server's own tool schema.
Why list_todos is rated Low
This tool retrieves and queries todo items for a tenant without creating, modifying, or deleting any data. It has no side effects beyond reading and presenting information. The required agent_id parameter is for scoping the read operation, not for destructive action. Blast radius if misused is minimal—an agent could at worst enumerate tasks but cannot alter business state.
From the tool's definition Tool name is 'list_todos' and description states it 'Returns todos' with filtering capability. The verb 'Returns' and phrases 'render a kanban view', 'find your assignments', or 'pick the next thing to work on' all indicate query/retrieval operations with no…
Attacks that exploit this kind of access
The rule that runs list_todos 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 list_todos, this is the rule to start with:
list_todos is read-only, so it stays allowed. 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 list_todos call is checked against it from then on.
Questions about list_todos
Returns todos for this tenant, optionally filtered by status. Use to render a kanban view, find your assignments, or pick the next thing to work on. agent_id required. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
list_todos accepts 4 parameters: limit, status, agent_id, assigned_to_agent_id. Required: 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 list_todos: 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.
list_todos is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_todos 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 list_todos. 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.
list_todos 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