complete_reminder
Marks a reminder complete in Apple Reminders (Reminders.app). Requires confirm=true. For Microsoft To Do use todo_complete_task instead.
This record as markdown: /tools/com-local-mcp-local-mcp/complete-reminder.md
What complete_reminder does on Local
AI agents use complete_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 |
|---|---|---|---|
confirm | boolean | — | Must be true to complete |
reminder_id | string | Yes | Reminder ID from list_reminders |
Parameters from the server's own tool schema.
Why complete_reminder is rated Medium
The tool performs a state modification on existing data (marking a reminder as complete), which constitutes a Write operation. It is reversible and has a localized scope (affects only one reminder), making it medium severity. The requirement for confirm=true demonstrates awareness of potential misuse.
From the tool's definition Tool description states it "Marks a reminder complete in Apple Reminders", which modifies the state of an existing reminder from incomplete to complete. This is a reversible change (the reminder can be marked incomplete again).
Attacks that exploit this kind of access
The rule that runs complete_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 complete_reminder, this is the rule to start with:
complete_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 complete_reminder call is checked against it from then on.
Questions about complete_reminder
Marks a reminder complete in Apple Reminders (Reminders.app). Requires confirm=true. For Microsoft To Do use todo_complete_task instead. 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.
complete_reminder accepts 2 parameters: confirm, reminder_id. Required: reminder_id. 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 complete_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.
complete_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 complete_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 complete_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.
complete_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