AI agents use update_task to create or update resources in Todo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todo environment.
This tool modifies existing tasks reversibly without deleting data or executing external code. It falls under Write category. Severity is medium because task updates could affect workflows or schedules, but the impact is contained to task metadata and is reversible. Confidence is high based on clear naming and the explicit mention of CRUD operations in server description.
From the tool's definition Tool name 'update_task' and description 'Update a task' indicate modification of existing task data. The server description confirms 'full CRUD operations' with write capability.
Attacks that exploit this kind of access
Update a task. It is categorised as a Write tool in the Todo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todo 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 Todo. 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 Todo MCP server (jc1122/todo-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 →