完成待办事项
AI agents use complete_todo to create or update resources in MCP Reminder — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Reminder environment.
This tool modifies existing task data by marking it as complete, which is a reversible state change (a todo can presumably be un-completed or re-opened). This fits the Write category as it creates or modifies data reversibly. Severity is medium because misuse could lead to important tasks being incorrectly marked complete, affecting task management but without financial or destructive consequences.
From the tool's definition Tool name 'complete_todo' and description '完成待办事项' (which translates to 'complete todo item') indicates modification of todo item state from incomplete to complete.
Attacks that exploit this kind of access
完成待办事项. It is categorised as a Write tool in the MCP Reminder MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Reminder 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 MCP Reminder. 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 MCP Reminder MCP server (sheacoding/mcp-reminder). 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 →