Create a new calendar event. Before using this tool, make sure to: 1. Ask the user which calendar they want to use if not specified (check calendars://list) 2. Ask if they want to add a location if none provided 3. Ask if they want to add any notes/description if none provided 4. Confirm the date...
AI agents use create_event to create or update resources in MCP iCal Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP iCal Server environment.
Creating calendar events is a Write operation—it modifies the calendar state by adding new entries, but changes are reversible (events can be deleted or edited). Severity is medium because misuse could create numerous unwanted calendar entries causing scheduling confusion or calendar spam, but does not result in financial loss, data destruction, or code execution.
From the tool's definition Tool description states 'Create a new calendar event' with arguments for title, start_time, end_time, and optional notes. This is a create operation that adds new data to the user's calendar system.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access create_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP iCal Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_event:
{
"version": "1",
"default": "deny",
"tools": {
"create_event": {
"limits": [
{
"counter": "create_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Free to start. No card required.
Create a new calendar event. Before using this tool, make sure to: 1. Ask the user which calendar they want to use if not specified (check calendars://list) 2. Ask if they want to add a location if none provided 3. Ask if they want to add any notes/description if none provided 4. Confirm the date and time with the user 5. Ask if they want to set reminders for the event Args: title: Event title start_time: Start time in ISO format (YYYY-MM-DDTHH:MM:SS) end_time: End time in ISO format (YYYY-MM-DDTHH:MM:SS) notes: Optional event notes/description. Ask user if they want to add notes. location: Optional event location. Ask user if they want to specify a location. calendar_name: Optional calendar name. Ask user which calendar to use, referencing calendars://list. all_day: Whether this is an all-day event reminder_offsets: List of minutes before the event to trigger reminders\ e.g. [60, 1440] means two reminders, the first 24 hours before the event and the second one hour before. recurrence_rule: Optional recurrence rule for the event. This should be an instance of RecurrenceRule with the following fields: - frequency: Frequency of the recurrence (e.g., DAILY, WEEKLY, MONTHLY, YEARLY). - interval: Interval between recurrences (e.g., every 2 weeks). - end_date: Optional end date for the recurrence. If specified, the recurrence will stop on this date. - occurrence_count: Optional number of occurrences. If specified, the recurrence will stop after this many occurrences. - days_of_week: Optional list of weekdays for the event. Use integers to represent days: - Sunday: 1 - Monday: 2 - Tuesday: 3 - Wednesday: 4 - Thursday: 5 - Friday: 6 - Saturday: 7 Note: Both end_date and occurrence_count should not be set simultaneously; choose one or the other, or leave both unset. It is categorised as a Write tool in the MCP iCal Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP iCal Server MCP server in PolicyLayer and add a rule for create_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 MCP iCal Server. Nothing to install.
create_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_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_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_event is provided by the MCP iCal Server MCP server (omar-v2/mcp-ical). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 MCP iCal Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 MCP iCal Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.