create_recurring_event
Create a recurring calendar event 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-event.md
What create_recurring_event does on Iconnect
AI agents use create_recurring_event 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_event is rated Medium
This tool creates calendar events, which is a Write operation—it adds new data to the system reversibly (events can be deleted afterward). While not Destructive (events aren't irretrievably purged), it modifies persistent calendar state. Severity is medium because widespread calendar pollution by an errant agent could disrupt scheduling and require cleanup, but individual event creation is not catastrophic.
From the tool's definition Tool description states 'Create a recurring calendar event via EventKit,' indicating irreversible data creation in the calendar system. The term 'Create' combined with 'recurring event' demonstrates persistent modification of calendar state.
Attacks that exploit this kind of access
The rule that runs create_recurring_event 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_event, this is the rule to start with:
create_recurring_event 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_event call is checked against it from then on.
Questions about create_recurring_event
Create a recurring calendar event 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_event: 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_event 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_event 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_event. 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_event 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