set_early_reminder
AI agents use set_early_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 appears to modify reminder state by adjusting or setting an earlier time for a reminder. This is a reversible data modification (Write category), not a destructive operation. The severity is low because misuse would only affect the user's own reminder timing, with minimal blast radius and easy remediation.
From the tool's definition The tool name 'set_early_reminder' suggests creating or modifying a reminder with timing properties. The server description explicitly states it enables 'create, read, update, delete' operations.
Attacks that exploit this kind of access
set_early_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 set_early_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.
set_early_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 set_early_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 set_early_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.
set_early_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 →