list_todos
List YOUR to-dos from the /todo app (public.todos) — the shared "what to do / what's done" list you + the user both maintain. Owner-scoped to the calling account. Filters: status (open|in_progress|done|blocked), priority (low|medium|high|urgent), source (user|claude|ask), tag (one tag to match). ...
This record as markdown: /tools/dev-busymate-busymate-devtools/list-todos.md
What list_todos does on Busymate DevTools
AI agents call list_todos to retrieve information from Busymate DevTools 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 |
|---|---|---|---|
tag | string | — | Only todos carrying this tag. |
limit | number | — | Max rows (default 200, cap 500). |
source | string | — | Filter by who added it. |
status | string | — | Filter by status. |
priority | string | — | Filter by priority. |
include_done | boolean | — | Include completed todos (default false hides them). |
Parameters from the server's own tool schema.
Why list_todos is rated Low
This tool purely retrieves and queries data from a shared todo list maintained by the calling account. It performs read-only operations with filters for status, priority, source, and tags. There are no side effects, modifications, or irreversible actions. The blast radius of misuse is minimal—an AI agent could only view todos, not alter them. This is a straightforward Read category tool with low severity.
From the tool's definition Tool name is `list_todos` and description states it "List YOUR to-dos from the /todo app" with filtering capabilities. The tool retrieves and queries todo items with no modification, creation, or deletion capability mentioned.
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 Busymate DevTools, 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 Busymate DevTools, apply this rule, and every list_todos call is checked against it from then on.
Questions about list_todos
List YOUR to-dos from the /todo app (public.todos) — the shared "what to do / what's done" list you + the user both maintain. Owner-scoped to the calling account. Filters: status (open|in_progress|done|blocked), priority (low|medium|high|urgent), source (user|claude|ask), tag (one tag to match). By DEFAULT hides completed todos (the active worklist); pass include_done:true (or an explicit status) to include them. Ordered by manual position (nulls last) then newest-first. Returns { count, todos:[{id,owner,title,notes,status,priority,tags,source,position,due_at,created_at,updated_at,done_at}] }. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
list_todos accepts 6 parameters: tag, limit, source, status, priority, include_done. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools 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 Busymate DevTools. 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 Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue