AI agents use complete_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 data (task completion status) but the change is reversible, making it Write rather than Destructive. The severity is medium because completing tasks could affect workflows or notifications, but the blast radius is limited to individual task state within a to-do application. Confidence is high because the description clearly indicates a state modification operation.
From the tool's definition Tool description states 'Mark a task as completed', which modifies task state. The server description confirms 'full CRUD operations' where this is the Update (U) portion. The action is reversible—tasks can be marked incomplete again.
Attacks that exploit this kind of access
Mark a task as completed. 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 complete_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.
complete_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 complete_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 complete_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.
complete_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 →