create_recurring_event
Create a new recurring calendar event with RFC5545 RRULE rules. Description supports markdown. Optional calendarId targets a specific calendar; when omitted, the event uses the authenticated user
This record as markdown: /tools/dugynoo-huly-mcp/create-recurring-event.md
What create_recurring_event does on Huly
AI agents use create_recurring_event to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why create_recurring_event is rated Medium
This is a Write operation because it creates calendar events that can be modified or deleted later (reversible). Severity is medium because misuse could spam calendars with unwanted recurring events, disrupting scheduling across the calendar and potentially other users' views if targeting shared calendars, but the action itself is not destructive or financial.
From the tool's definition Tool name is 'create_recurring_event' and description states 'Create a new recurring calendar event' — a write operation that creates calendar data. The tool creates repeating calendar entries via RFC5545 RRULE rules with optional calendar targeting.
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 Huly, 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 Huly, apply this rule, and every create_recurring_event call is checked against it from then on.
Questions about create_recurring_event
Create a new recurring calendar event with RFC5545 RRULE rules. Description supports markdown. Optional calendarId targets a specific calendar; when omitted, the event uses the authenticated user. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly 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 Huly. 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 Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue