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 My MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your My MCP environment.
The tool creates or modifies data in a reversible manner by updating a task list name. This is characteristic of Write category tools. Severity is medium because modifying organizational metadata in a personal task management tool has limited blast radius — the change can be undone and does not affect financial systems, destroy data permanently, or execute arbitrary code.
From the tool's definition Tool description states 'Update the name of an existing task list' — this modifies data (the task list name) reversibly without deleting or destroying the underlying list or its contents.
Documented attack patterns abuse exactly the kind of access update-task-list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and My MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for update-task-list:
{
"version": "1",
"default": "deny",
"tools": {
"update-task-list": {
"limits": [
{
"counter": "update-task-list_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-task-list 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.
Free to start. No card required.
Update the name of an existing task list (top-level container) in Microsoft Todo. It is categorised as a Write tool in the My MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the My 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 My MCP. 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 My MCP server (jordanburke/microsoft-todo-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from My MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 My MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.