创建一条提醒事项。
AI agents use create_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.
This tool creates new reminder entries in the macOS Reminders application. Creation is a reversible write operation (reminders can be deleted via delete_reminder). It does not execute arbitrary code, delete data irreversibly, or move money. Severity is medium because an agent could spam reminders or create misleading reminders, but the impact is contained to a single user's reminder list and is easily undone.
From the tool's definition Tool name is 'create_reminder' and server description states it exposes 'CRUD operations' including create. The Chinese description '创建一条提醒事项' translates to 'create a reminder item', confirming write semantics.
Attacks that exploit this kind of access
创建一条提醒事项。. 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 create_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.
create_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 create_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 create_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.
create_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 →