This record as markdown: /tools/jo3zik-ms-365-mcp-server/delete-todo-task.md
What delete-todo-task does on Ms 365
AI agents call delete-todo-task to permanently remove resources in Ms 365, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
confirm | boolean | — | For destructive operations when the confirm gate is enabled (MS365_MCP_REQUIRE_CONFIRM=true; off by default). Set to true only after the user has explicitly app |
If-Match | string | — | ETag |
todoTaskId | string | Yes | Value for the 'todoTaskId' path segment. Pass it under the name 'todoTaskId', not as 'id'. Use the 'id' field of the todo task object as returned by Microsoft G |
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 delete-todo-task is rated Critical
An AI agent that decides to call delete-todo-task doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Ms 365 is gone. There is no undo for destructive operations.
Attacks that exploit this kind of access
The rule that runs delete-todo-task 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 delete-todo-task, this is the rule to start with:
delete-todo-task is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Ms 365, apply this rule, and every delete-todo-task call is checked against it from then on.
Questions about delete-todo-task
Delete a todoTask object. It is categorised as a Destructive tool in the Ms 365 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete-todo-task accepts 6 parameters: confirm, If-Match, todoTaskId, includeHeaders, todoTaskListId, excludeResponse. Required: todoTaskId, 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 delete-todo-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 Ms 365. Nothing to install.
delete-todo-task is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete-todo-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 delete-todo-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.
delete-todo-task 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.
Across the catalogue