create_recurring_reminder
Create a recurring reminder via EventKit. Supports daily, weekly, monthly, and yearly recurrence with configurable intervals. Requires macOS 26+ Swift bridge.
This record as markdown: /tools/io-github-heznpc-iconnect/create-recurring-reminder.md
What create_recurring_reminder does on Iconnect
AI agents use create_recurring_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 create_recurring_reminder is rated Medium
This tool creates a new recurring reminder, which is a reversible write operation. It modifies the user's calendar/reminder system by adding new data but does not execute arbitrary code, delete data irreversibly, or move funds. The severity is medium because misconfiguration or abuse could spam the user's reminders, but the impact is limited to calendar data and easily reversible by deletion.
From the tool's definition Tool creates a recurring reminder via EventKit with configurable recurrence patterns (daily, weekly, monthly, yearly). The verb 'create' and the phrase 'Create a recurring reminder' directly indicate data creation.
Attacks that exploit this kind of access
The rule that runs create_recurring_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 create_recurring_reminder, this is the rule to start with:
create_recurring_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 create_recurring_reminder call is checked against it from then on.
Questions about create_recurring_reminder
Create a recurring reminder via EventKit. Supports daily, weekly, monthly, and yearly recurrence with configurable intervals. Requires macOS 26+ Swift bridge. 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 create_recurring_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.
create_recurring_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_recurring_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_recurring_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_recurring_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