标记指定 id 的提醒事项为已完成。
AI agents use complete_reminder 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.
Completing a reminder updates its status/state but does not delete or destroy data. It is reversible (can be un-completed). This is a modification operation, fitting the Write category. Severity is low because the blast radius is limited to toggling a single reminder's completion status, with no financial impact, data loss, or code execution.
From the tool's definition Tool marks a reminder as complete ("标记指定 id 的提醒事项为已完成" = mark reminder with specified ID as completed). This modifies the state of an existing reminder record reversibly—the action can be undone by unmarking it as complete.
Attacks that exploit this kind of access
标记指定 id 的提醒事项为已完成。. 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 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 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 Apple Reminders MCP server (yzheeng/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 →