Update an existing task in Microsoft Todo. Allows changing any properties of the task including title, due date, importance, etc.
AI agents use update-task to create or update resources in Microsoft Todo MCP Service — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Microsoft Todo MCP Service environment.
This tool creates or modifies data reversibly within a task management system. Users can change task properties like title, due date, and importance, but these changes are non-destructive and can be undone by updating again. There is no permanent deletion, code execution, or financial impact. This fits the Write category as a classic update/modify operation.
From the tool's definition Tool name 'update-task' and description stating 'Update an existing task' and 'Allows changing any properties of the task including title, due date, importance, etc.' clearly indicate modification of existing data.
Documented attack patterns abuse exactly the kind of access update-task gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Microsoft Todo MCP Service, and nothing reaches the server without passing your rules. This is the rule we recommend for update-task:
{
"version": "1",
"default": "deny",
"tools": {
"update-task": {
"limits": [
{
"counter": "update-task_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update-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.
Free to start. No card required.
Update an existing task in Microsoft Todo. Allows changing any properties of the task including title, due date, importance, etc. It is categorised as a Write tool in the Microsoft Todo MCP Service MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Microsoft Todo MCP Service MCP server in PolicyLayer and add a rule for update-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 Microsoft Todo MCP Service. Nothing to install.
update-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 update-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 update-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.
update-task is provided by the Microsoft Todo MCP Service MCP server (jhirono/todomcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Microsoft Todo MCP Service, 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.
13 Microsoft Todo MCP Service tools catalogued and risk-classified — across an index of 43,000+ MCP servers.