process_reminders · Todos MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why process_reminders needs a policy

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

Recommended rule Ready

Verdict

process_reminders Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "process_reminders": {
      "limits": [
        {
          "counter": "process_reminders_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Todos, so you can run agents against it safely.

FAQ

Questions about process_reminders

What does the process_reminders tool do? +

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.

How do I enforce a policy on process_reminders? +

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.

What risk level is process_reminders? +

process_reminders is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit process_reminders? +

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.

How do I block process_reminders completely? +

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.

What MCP server provides process_reminders? +

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.