// SCAN REPORT

MCP Reminders

7 tools. 5 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

5 can modify or destroy data

2 read-only

7 tools total

Community server · catalogue entry verified 29/06/2026

How to control MCP Reminders ↓

TOOL MAP

What MCP Reminders exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous MCP Reminders tools

Destructive · Low clear_old_reminders This tool performs a permanent deletion operation (clear) on past reminder data. Destructive · Low delete_reminder While the tool deletes reminders (data that cannot be recovered once deleted), the impact is limited to the user's own reminder system—a low-blast-radius operation with no risk to other systems, financial data, or extern Write · Low complete_reminder Completing a reminder updates metadata about that reminder's status. Write · Medium move_to_notes The action is reversible (notes can be edited or deleted later) and creates/modifies data rather than executing arbitrary code or destroying data.

5 of MCP Reminders's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control MCP Reminders

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Reminders, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "clear_old_reminders": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "complete_reminder": {
    "limits": [
      {
        "counter": "complete_reminder_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "check_reminders": {
    "limits": [
      {
        "counter": "check_reminders_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register MCP Reminders — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MCP REMINDERS →

Instant setup, no code required.

FULL CATALOGUE

All 7 MCP Reminders tools

DESTRUCTIVE 2 tools

Destructive clear_old_reminders Clear old completed/moved reminders Destructive delete_reminder Delete a reminder

WRITE 3 tools

Write complete_reminder Mark a reminder as completed Write move_to_notes Move reminder to permanent notes Write remind_me Add a reminder

READ 2 tools

Read check_reminders Check your reminders Read help Get help on using reminders

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about MCP Reminders

Can an AI agent delete data through the MCP Reminders MCP server? +

Yes. The MCP Reminders server exposes 2 destructive tools including clear_old_reminders, delete_reminder. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through MCP Reminders? +

The MCP Reminders server has 3 write tools including complete_reminder, move_to_notes, remind_me. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach MCP Reminders.

How many tools does the MCP Reminders MCP server expose? +

7 tools across 3 categories: Destructive, Read, Write. 2 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on MCP Reminders? +

Register the MCP Reminders MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every MCP Reminders tool call.

Deterministic rules across all 7 MCP Reminders tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP REMINDERS →

Instant setup, no code required.

7 MCP Reminders tools catalogued and risk-classified — across an index of 43,000+ MCP servers.