todo_create_task
Creates a task in Microsoft To Do (via Reminders sync). Task appears in To Do automatically once synced.
This record as markdown: /tools/com-local-mcp-local-mcp/todo-create-task.md
What todo_create_task does on Local
AI agents use todo_create_task to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
list | string | — | List name (from todo_list_lists). Defaults to first available list. |
notes | string | — | Task notes (optional) |
title | string | Yes | Task title |
confirm | boolean | — | Must be true to create |
due_date | string | — | Due date (YYYY-MM-DD, optional) |
priority | integer | — | Priority: 1=high, 5=medium, 9=low (optional) |
Parameters from the server's own tool schema.
Why todo_create_task is rated Medium
This tool creates new tasks in Microsoft To Do through the Reminders sync mechanism. Task creation is a Write operation (reversible modification), not Execute (no code/command execution), not Destructive (tasks can be deleted), and not Financial (no money involved). Low severity because misuse would result in unwanted task entries that can be easily removed, with minimal impact on user operations or data integrity.
From the tool's definition Tool name 'todo_create_task' and description explicitly states 'Creates a task' — a reversible data creation operation. Task appears in the To Do application upon sync.
Attacks that exploit this kind of access
The rule that runs todo_create_task 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_create_task, this is the rule to start with:
todo_create_task stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_create_task call is checked against it from then on.
Questions about todo_create_task
Creates a task in Microsoft To Do (via Reminders sync). Task appears in To Do automatically once synced. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
todo_create_task accepts 6 parameters: list, notes, title, confirm, due_date, priority. Required: title. 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_create_task: 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_create_task 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 todo_create_task 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_create_task. 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_create_task 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