Mark a todo as complete.
AI agents use complete_todo to create or update resources in Next Js Todo MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Next Js Todo MCP Server environment.
Marking a todo as complete modifies the todo item's state (reversibly) but does not create new data, delete data irreversibly, execute arbitrary code, or move money. It is a standard Write operation. While the server supports delete operations (Destructive category), this specific tool only updates a boolean or status flag on an existing record, making it reversible and therefore Write rather than Destructive.
From the tool's definition Tool description states 'Mark a todo as complete.' This is a state-change operation that updates an existing todo item's completion status.
Attacks that exploit this kind of access
Mark a todo as complete. It is categorised as a Write tool in the Next Js Todo MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Next Js Todo MCP Server MCP server in PolicyLayer and add a rule for complete_todo: 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 Next Js Todo MCP Server. Nothing to install.
complete_todo 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_todo 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_todo. 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_todo is provided by the Next Js Todo MCP Server MCP server (repaera/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 →