update_reminder
AI agents use update_reminder to create or update resources in MCP Apple Reminders — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Apple Reminders environment.
This tool updates reminders, which is a reversible modification of data. It falls under Write category rather than Destructive since updates can be undone by updating again to previous values. Severity is medium because misuse could modify important personal reminders but the blast radius is limited to the user's local reminders.
From the tool's definition Tool name 'update_reminder' combined with server description stating the server enables 'create, read, update, delete' operations on Apple Reminders. The tool directly modifies existing reminder data.
Attacks that exploit this kind of access
update_reminder. It is categorised as a Write tool in the MCP Apple Reminders MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Apple Reminders 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 MCP Apple Reminders. Nothing to install.
update_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 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.
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.
update_reminder is provided by the MCP Apple Reminders MCP server (rex/mcp-apple-reminders). 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 →