list-todo-tasks
Get the todoTask resources from the tasks navigation property of a specified todoTaskList. 💡 TIP: Lists tasks in a To Do list. Requires todoTaskList-id — use list-todo-task-lists to find it. NOTE: $select is NOT supported — do not pass select, Graph returns 400. Use $filter=status eq 'notStarted...
This record as markdown: /tools/jo3zik-ms-365-mcp-server/list-todo-tasks.md
What list-todo-tasks does on Ms 365
AI agents call list-todo-tasks to retrieve information from Ms 365 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 |
|---|---|---|---|
top | number | — | Page size (Graph $top). Start small (e.g. 5–15) so responses fit the model context; raise only if needed. Use $select to return fewer fields per item. For more |
skip | number | — | Items to skip for pagination. Not supported with $search. |
count | boolean | — | Set true to enable advanced query mode (ConsistencyLevel: eventual). Required for complex $filter on flag/flagStatus or contains(). |
expand | array | — | Navigation properties to inline, e.g. attachments on a message or event. Only navigation properties can be expanded: expanding a non-navigation property such as |
filter | string | — | OData filter expression. Add $count=true for advanced filters (flag/flagStatus, contains()). Cannot combine with $search. |
search | string | — | KQL search query — wrap value in double quotes. Cannot combine with $filter. |
select | string | — | Comma-separated fields to return, e.g. id,subject,from,receivedDateTime |
orderby | string | — | Sort expression, e.g. receivedDateTime desc |
fetchAllPages | boolean | — | Follow @odata.nextLink and merge up to 100 pages into one response. Can return enormous payloads—only when the user explicitly needs a full export. Prefer a sma |
includeHeaders | boolean | — | Include response headers (including ETag) in the response metadata |
todoTaskListId | string | Yes | Value for the 'todoTaskListId' path segment. Pass it under the name 'todoTaskListId', not as 'id'. Use the 'id' field of the todo task list object as returned b |
excludeResponse | boolean | — | Exclude the full response body and only return success or failure indication |
Parameters from the server's own tool schema.
Why list-todo-tasks is rated Low
Even though list-todo-tasks only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs list-todo-tasks safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ms 365, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list-todo-tasks, this is the rule to start with:
list-todo-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 Ms 365, apply this rule, and every list-todo-tasks call is checked against it from then on.
Questions about list-todo-tasks
Get the todoTask resources from the tasks navigation property of a specified todoTaskList. 💡 TIP: Lists tasks in a To Do list. Requires todoTaskList-id — use list-todo-task-lists to find it. NOTE: $select is NOT supported — do not pass select, Graph returns 400. Use $filter=status eq 'notStarted' or $filter=status eq 'completed' to filter by status. Use $top to limit results. Status values: 'notStarted', 'inProgress', 'completed', 'waitingOnOthers', 'deferred'. It is categorised as a Read tool in the Ms 365 MCP Server, which means it retrieves data without modifying state.
list-todo-tasks accepts 12 parameters: top, skip, count, expand, filter, search, select, orderby, fetchAllPages, includeHeaders, todoTaskListId, excludeResponse. Required: todoTaskListId. The full parameter table on this page comes from the server's own tool schema.
Register the Ms 365 MCP server in PolicyLayer and add a rule for list-todo-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 Ms 365. Nothing to install.
list-todo-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 list-todo-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 list-todo-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.
list-todo-tasks is provided by the Ms 365 MCP server (@jo3zik/ms-365-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ms 365, and thousands of servers like it.
This server
Across the catalogue