Update an existing reminder in Apple Reminders
AI agents use updateReminder to create or update resources in Apple Reminders MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Reminders MCP Server environment.
This tool modifies existing data (reminder properties) in a reversible manner. Updates can be undone by updating again with different values or reverting to previous state, which distinguishes it from destructive deletion. While the sibling deleteReminder falls into Destructive, updateReminder is clearly a Write operation.
From the tool's definition Tool description states it will 'Update an existing reminder in Apple Reminders', and server description confirms it can perform 'updating' operations on reminders.
Attacks that exploit this kind of access
Update an existing reminder in Apple Reminders. It is categorised as a Write tool in the Apple Reminders MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apple Reminders MCP Server MCP server in PolicyLayer and add a rule for updateReminder: 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 Apple Reminders MCP Server. Nothing to install.
updateReminder 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 updateReminder 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 updateReminder. 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.
updateReminder is provided by the Apple Reminders MCP Server MCP server (leawn/apple_reminders_mcp). 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 →