update_reminder
Update fields of an existing reminder in Apple Reminders — a write to user data; only the fields you pass change. Set dueDate to null to clear it. Recurrence rules cannot be modified via automation.
This record as markdown: /tools/io-github-heznpc-iconnect/update-reminder.md
What update_reminder does on Iconnect
AI agents use update_reminder to create or update resources in Iconnect, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Iconnect environment.
Why update_reminder is rated Medium
This tool modifies existing reminders reversibly (updates fields without deletion). It does not delete data (making it not Destructive), execute arbitrary code (not Execute), move money (not Financial), or trigger external operations (not Execute). The blast radius is medium because misuse could alter important user reminders, but changes are reversible and limited to the reminder system.
From the tool's definition Tool description states 'Update fields of an existing reminder in Apple Reminders — a write to user data; only the fields you pass change.' The word 'Update' and explicit mention of 'write to user data' confirm Write category.
Attacks that exploit this kind of access
The rule that runs update_reminder safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_reminder, this is the rule to start with:
update_reminder stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every update_reminder call is checked against it from then on.
Questions about update_reminder
Update fields of an existing reminder in Apple Reminders — a write to user data; only the fields you pass change. Set dueDate to null to clear it. Recurrence rules cannot be modified via automation. It is categorised as a Write tool in the Iconnect MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Iconnect 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 Iconnect. 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 Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
This server
Across the catalogue