Update an existing reminder
AI agents use apple_reminders_update to create or update resources in Apple Reminders — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Reminders environment.
This tool modifies existing data (reminders) in a reversible manner. Updates can typically be undone by making further updates or restores. It is not destructive (no deletion), does not execute arbitrary code, and has no financial impact. It falls squarely in the Write category. Severity is medium because an agent could modify many reminders, causing confusion or data loss, but changes are typically reversible.
From the tool's definition Tool name is 'apple_reminders_update' with description 'Update an existing reminder'. The server provides 'CRUD operations' including modification of reminders.
Attacks that exploit this kind of access
Update an existing reminder. It is categorised as a Write tool in the Apple Reminders MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apple Reminders MCP server in PolicyLayer and add a rule for apple_reminders_update: 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. Nothing to install.
apple_reminders_update 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 apple_reminders_update 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 apple_reminders_update. 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.
apple_reminders_update is provided by the Apple Reminders MCP server (mggrim/apple-reminders-mcp-server). 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 →