添加待办事项
AI agents use add_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.
Adding a todo item is a Write operation: it creates new data in the persistent storage of the reminder system. It is not Read (doesn't only query), not Execute (doesn't run external code or shell commands), not Destructive (the addition is reversible via deletion/completion), and not Financial. Severity is low because misuse would only create unwanted task entries, which are easily cleaned up without material impact.
From the tool's definition Tool name 'add_todo' and description '添加待办事项' (meaning 'add todo item') indicate creating a new task/reminder entry. This is a reversible data creation operation with no side effects beyond writing to a task list.
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 add_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.
add_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 add_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 add_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.
add_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 →