Mark a reminder as completed.
AI agents use complete_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.
While this tool modifies data, the change is reversible (reminders can be marked incomplete again), placing it in the Write category rather than Destructive. The blast radius is low: marking reminders as complete has minimal side effects and poses negligible security or operational risk.
From the tool's definition Tool description states 'Mark a reminder as completed.' This modifies the state of a reminder by changing its completion status, which is a reversible write operation. The user can uncomplete the reminder later.
Attacks that exploit this kind of access
Mark a reminder as completed. 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 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 MCP Apple Reminders. 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 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 →