process_reminders
Fire due local reminders; optional desktop notify-send when enabled.
This record as markdown: /tools/todos/process-reminders.md
What process_reminders does on Todos
AI agents invoke process_reminders to trigger actions in Todos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why process_reminders is rated High
The tool actively fires/triggers reminders and can invoke desktop notification commands (notify-send), which constitutes executing external operations. It is not purely reading data, and the side effects (triggering notifications, marking reminders as fired) make Execute the most appropriate category.
From the tool's definition "Fire due local reminders" and "optional desktop notify-send when enabled" — triggers external operations (firing reminders, sending desktop notifications)
Attacks that exploit this kind of access
The rule that runs process_reminders safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For process_reminders, this is the rule to start with:
process_reminders stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every process_reminders call is checked against it from then on.
Questions about process_reminders
Fire due local reminders; optional desktop notify-send when enabled. It is categorised as a Execute tool in the Todos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Todos MCP server in PolicyLayer and add a rule for process_reminders: 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 Todos. Nothing to install.
process_reminders is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the process_reminders 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 process_reminders. 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.
process_reminders is provided by the Todos MCP server (@hasna/todos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Todos, and thousands of servers like it.
Across the catalogue