update_reminder

Updates an existing reminder in Reminders.app. Change the title, due date, notes, priority, or move it to another list (list_name). Get reminder_id from list_reminders. Requires confirm=true.

SERVERLocal SOURCElocal-mcp

Medium RISK CLASS

Category Write

Parameters 71 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-local-mcp-local-mcp/update-reminder.md

WHAT IT DOES

What update_reminder does on Local

AI agents use update_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	—	New notes text (optional)
`title`	string	—	New title (optional)
`confirm`	boolean	—	Must be true to apply changes
`due_date`	string	—	New ISO 8601 due date. Pass empty string to clear (optional)
`priority`	string	—	Priority: none \| low \| medium \| high (optional)
`list_name`	string	—	Move the reminder to this list (a name from list_reminder_lists) (optional)
`reminder_id`	string	Yes	Reminder identifier from list_reminders

Parameters from the server's own tool schema.

RISK

Why update_reminder is rated Medium

This tool modifies existing reminder records in Reminders.app. The changes (updating title, due date, notes, priority, list assignment) are all reversible and do not permanently delete data or execute arbitrary code. The requirement for confirm=true is a safety measure but doesn't change the fundamental Write category.

From the tool's definition Tool description explicitly states it 'Updates an existing reminder' and allows changes to 'title, due date, notes, priority, or move it to another list'. These are reversible modifications to calendar/reminder data, characteristic of Write operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_reminder, this is the rule to start with:

update_reminder Rate-limited

update_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_reminder": {
      "limits": [
        {
          "counter": "update_reminder_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Local, apply this rule, and every update_reminder call is checked against it from then on.

FAQ

Questions about update_reminder

What does the update_reminder tool do? +

Updates an existing reminder in Reminders.app. Change the title, due date, notes, priority, or move it to another list (list_name). Get reminder_id from list_reminders. Requires confirm=true. 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.

What parameters does update_reminder accept? +

update_reminder accepts 7 parameters: notes, title, confirm, due_date, priority, list_name, reminder_id. Required: reminder_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_reminder? +

Register the Local MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_reminder? +

update_reminder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_reminder? +

Yes. Add a rate_limit block to the update_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.

How do I block update_reminder completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_reminder? +

update_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.

KEEP EXPLORING

More on Local, and thousands of servers like it.

This server

All 234 Local tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →