todo_list_tasks
Lists tasks from a Microsoft To Do list (or any Reminders list). Syncs via macOS Reminders.
This record as markdown: /tools/com-local-mcp-local-mcp/todo-list-tasks.md
What todo_list_tasks does on Local
AI agents call todo_list_tasks to retrieve information from Local 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 |
|---|---|---|---|
list | string | — | List name (from todo_list_lists). Leave empty to show all. |
limit | integer | — | Max tasks to return (default 50) |
include_completed | boolean | — | Include completed tasks (default false) |
Parameters from the server's own tool schema.
Why todo_list_tasks is rated Low
This tool retrieves and queries task data from Microsoft To Do or macOS Reminders. It performs a read-only operation (list) with no capability to create, modify, delete, or execute actions. The blast radius of misuse is minimal—an agent could only view task information it is already authorized to access. This is a standard Read category tool.
From the tool's definition Tool description states it 'Lists tasks' from a To Do/Reminders list. The verb 'Lists' indicates data retrieval without modification or side effects.
Attacks that exploit this kind of access
The rule that runs todo_list_tasks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For todo_list_tasks, this is the rule to start with:
todo_list_tasks 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 Local, apply this rule, and every todo_list_tasks call is checked against it from then on.
Questions about todo_list_tasks
Lists tasks from a Microsoft To Do list (or any Reminders list). Syncs via macOS Reminders. It is categorised as a Read tool in the Local MCP Server, which means it retrieves data without modifying state.
todo_list_tasks accepts 3 parameters: list, limit, include_completed. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for todo_list_tasks: 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 Local. Nothing to install.
todo_list_tasks 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 todo_list_tasks 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 todo_list_tasks. 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.
todo_list_tasks is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue