create_event

Create a new calendar event in Nextcloud with date/time, location, description, attendees, and optional recurrence.

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

Medium RISK CLASS

Category Write

Parameters 122 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiquila-nextcloud-mcp-server/create-event.md

WHAT IT DOES

What create_event does on AIquila — Nextcloud MCP Server

AI agents use create_event to create or update resources in AIquila — Nextcloud MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AIquila — Nextcloud MCP Server environment.

Parameter	Type	Required	Description
`tzid`	string	—	IANA time zone (e.g. "Europe/Berlin"). When set, a VTIMEZONE block is emitted and dtstart/dtend use TZID instead of UTC. Required for reliable iOS Calendar and
`alarm`	number	—	Single reminder in minutes before the event (e.g. 15 for 15 min before). For multiple reminders use alarms[].
`dtend`	string	—	End date/time. For all-day events, this is the exclusive end date (day after last day). If omitted, defaults to 1 hour after start (timed) or next day (all-day)
`rrule`	string	—	Recurrence rule (e.g. 'FREQ=WEEKLY;BYDAY=MO,WE,FR' or 'FREQ=MONTHLY;COUNT=12')
`alarms`	array	—	Multiple reminders in minutes before the event (e.g. [1440, 60] for 1 day and 1 hour before). Combined with alarm if both are set.
`status`	string	—	Event status (default: CONFIRMED)
`transp`	string	—	Time transparency for free/busy (OPAQUE = busy, TRANSPARENT = free)
`dtstart`	string	Yes	Start date/time in YYYYMMDD (all-day) or YYYYMMDDTHHmmssZ (timed) format
`summary`	string	Yes	The event title
`location`	string	—	Event location
`attendees`	array	—	List of attendees
`categories`	array	—	Tags/categories

Parameters from the server's own tool schema.

RISK

Why create_event is rated Medium

This tool creates new calendar entries in Nextcloud, which constitutes data modification. It is categorized as Write rather than Execute because it modifies calendar data through a structured, reversible operation rather than executing arbitrary commands. The severity is medium because misuse could clutter calendars or create misleading scheduling entries, but the impact is limited in scope and reversible.

From the tool's definition Tool creates a new calendar event with date/time, location, description, attendees, and optional recurrence. The description uses 'Create a new calendar event', which indicates data creation.

Risk signalsHigh parameter count (19 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_event safely

PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_event, this is the rule to start with:

create_event Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_event": {
      "limits": [
        {
          "counter": "create_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every create_event call is checked against it from then on.

FAQ

Questions about create_event

What does the create_event tool do? +

Create a new calendar event in Nextcloud with date/time, location, description, attendees, and optional recurrence. It is categorised as a Write tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_event accept? +

create_event accepts 12 parameters: tzid, alarm, dtend, rrule, alarms, status, transp, dtstart, summary, location, attendees, categories. Required: dtstart, summary. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_event? +

Register the AIquila — Nextcloud MCP 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 AIquila — Nextcloud MCP Server. Nothing to install.

What risk level is create_event? +

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

Can I rate-limit create_event? +

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.

How do I block create_event completely? +

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.

What MCP server provides create_event? +

create_event is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on AIquila — Nextcloud MCP Server, and thousands of servers like it.

This server

All 301 AIquila — Nextcloud MCP Server tools →

Across the catalogue

calendar_create_event on Apple Apps MCP →create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →