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.

SERVERIconnect SOURCEiconnect-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about create_recurring_event

What does the create_recurring_event tool do? +

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.

How do I enforce a policy on create_recurring_event? +

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.

What risk level is create_recurring_event? +

create_recurring_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_recurring_event? +

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.

How do I block create_recurring_event completely? +

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.

What MCP server provides create_recurring_event? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Iconnect's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.