New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

list_actionable_todos

Returns the highest-priority unassigned open todos, ranked so an agent can pull the next best chip without relying on prose handoffs. This is the canonical pull lane of the Jobs board, the fleet's shared work queue (humans watch the same todos at /admin/jobs). When you take a chip, claim it with ...

SERVERUnClick SOURCE@unclick/mcp-server
Low RISK CLASS
Category Read
Parameters 31 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/list-actionable-todos.md

What list_actionable_todos does on UnClick

AI agents call list_actionable_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.

ParameterTypeRequiredDescription
limit number
agent_id string Yes
include_description boolean Include compact job descriptions so runners can keep the source brief while routing.

Parameters from the server's own tool schema.

Why list_actionable_todos is rated Low

This tool retrieves and lists existing todos from a shared work queue. While it serves as an entry point for workflow operations, the tool itself performs only a read operation—it queries data and returns results with no side effects. The description explicitly distinguishes this read action from state-modifying actions (claiming with update_todo, closing with complete_todo), which are separate tools.

From the tool's definition Tool description states it 'Returns the highest-priority unassigned open todos' and explicitly identifies itself as a pull operation ('This is the canonical pull lane of the Jobs board').

Risk signalsAdmin/system-level operation

Questions about list_actionable_todos

What does the list_actionable_todos tool do? +

Returns the highest-priority unassigned open todos, ranked so an agent can pull the next best chip without relying on prose handoffs. This is the canonical pull lane of the Jobs board, the fleet's shared work queue (humans watch the same todos at /admin/jobs). When you take a chip, claim it with update_todo (assign yourself, status in_progress) so the board shows one owner per job, and close it with complete_todo or a 'Closes UnClick todo: <uuid>' line in the merged PR body. agent_id required. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.

What parameters does list_actionable_todos accept? +

list_actionable_todos accepts 3 parameters: limit, agent_id, include_description. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_actionable_todos? +

Register the UnClick MCP server in PolicyLayer and add a rule for list_actionable_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.

What risk level is list_actionable_todos? +

list_actionable_todos is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_actionable_todos? +

Yes. Add a rate_limit block to the list_actionable_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.

How do I block list_actionable_todos completely? +

Set action: deny in the PolicyLayer policy for list_actionable_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.

What MCP server provides list_actionable_todos? +

list_actionable_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UnClick's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.