This record as markdown: /tools/com-local-mcp-local-mcp/create-reminder.md
What create_reminder does on Local
AI agents use create_reminder to create or update resources in Local, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Local environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
notes | string | — | Notes (optional) |
title | string | Yes | Reminder title |
confirm | boolean | — | Must be true to create |
due_date | string | — | ISO 8601 date (optional) |
priority | string | — | Priority: none | low | medium | high (optional) |
list_name | string | — | Reminder list name (optional) |
Parameters from the server's own tool schema.
Why create_reminder is rated Medium
This tool creates a new reminder entry in the Reminders application, which is a write operation that adds data to a local system. It is reversible (the reminder can be deleted later) and has minimal blast radius—creating unwanted reminders is inconvenient but not destructive or harmful. No financial, destructive, or code execution aspects are involved.
From the tool's definition Tool name 'create_reminder' and description 'Creates a reminder in Reminders.app' indicate data creation. The action is reversible (reminders can be deleted).
Attacks that exploit this kind of access
The rule that runs create_reminder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Local, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_reminder, this is the rule to start with:
create_reminder 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 Local, apply this rule, and every create_reminder call is checked against it from then on.
Questions about create_reminder
Creates a reminder in Reminders.app. It is categorised as a Write tool in the Local MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_reminder accepts 6 parameters: notes, title, confirm, due_date, priority, list_name. Required: title. The full parameter table on this page comes from the server's own tool schema.
Register the Local MCP server in PolicyLayer and add a rule for create_reminder: 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 Local. Nothing to install.
create_reminder 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 create_reminder 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 create_reminder. 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.
create_reminder is provided by the Local MCP server (local-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Local, and thousands of servers like it.
This server
Across the catalogue