scan_reminders
Scan tasks for due-date and SLA reminders; upsert local reminder records.
This record as markdown: /tools/todos/scan-reminders.md
What scan_reminders does on Todos
AI agents use scan_reminders to create or update resources in Todos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Todos environment.
Why scan_reminders is rated Medium
The tool scans tasks (read) but also upserts (creates or updates) local reminder records, which is a write operation. 'Upsert' means insert or update, making it reversible and fitting the Write category. Severity is medium as misuse could create spurious or erroneous reminder records affecting task management workflows.
From the tool's definition upsert local reminder records
Attacks that exploit this kind of access
The rule that runs scan_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 scan_reminders, this is the rule to start with:
scan_reminders stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 scan_reminders call is checked against it from then on.
Questions about scan_reminders
Scan tasks for due-date and SLA reminders; upsert local reminder records. It is categorised as a Write tool in the Todos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Todos MCP server in PolicyLayer and add a rule for scan_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.
scan_reminders 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 scan_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 scan_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.
scan_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.
This server
Across the catalogue