Update the name of an existing task list (top-level container) in Microsoft Todo.
AI agents use update-task-list to create or update resources in Microsoft Todo Safe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Microsoft Todo Safe environment.
Updating a task list name is a reversible modification operation that creates or modifies data without deleting or executing code. This falls squarely into the Write category. Severity is medium because task list names are low-criticality metadata, though unauthorized changes could disrupt user workflows.
From the tool's definition Tool description explicitly states 'Update the name of an existing task list' — this modifies data (task list name) reversibly.
Attacks that exploit this kind of access
Update the name of an existing task list (top-level container) in Microsoft Todo. It is categorised as a Write tool in the Microsoft Todo Safe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Microsoft Todo Safe MCP server in PolicyLayer and add a rule for update-task-list: 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 Microsoft Todo Safe. Nothing to install.
update-task-list 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 update-task-list 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 update-task-list. 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.
update-task-list is provided by the Microsoft Todo Safe MCP server (saenai/microsoft-todo-safe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →