Add a reminder
AI agents use remind_me to create or update resources in MCP Reminders — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Reminders environment.
This tool creates or modifies data (adds a reminder) in a reversible manner—reminders can be deleted, completed, or moved to notes. It has no destructive capability, does not execute external code or commands, and carries no financial impact. The blast radius of misuse is minimal (unwanted reminders in a personal notes system). Low severity is appropriate for a local reminder management tool.
From the tool's definition Tool name 'remind_me' and description 'Add a reminder' indicate creation of new reminder data. The sibling tools (check_reminders, complete_reminder, delete_reminder, move_to_notes) confirm this is a data management system where remind_me performs the write…
Attacks that exploit this kind of access
Add a reminder. It is categorised as a Write tool in the MCP Reminders MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Reminders MCP server in PolicyLayer and add a rule for remind_me: 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 Reminders. Nothing to install.
remind_me 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 remind_me 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 remind_me. 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.
remind_me is provided by the MCP Reminders MCP server (mikeybeez/mcp-reminders). 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 →