update_event

Update an existing calendar event's fields by UID. Uses CalDAV ETag-based optimistic concurrency.

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

Medium RISK CLASS

Category Write

Parameters 121 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/update-event.md

WHAT IT DOES

What update_event does on AIquila — Nextcloud MCP Server

AI agents use update_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
`uid`	string	Yes	The UID of the event to update
`tzid`	string	—	IANA time zone (e.g. "Europe/Berlin") for the updated dtstart/dtend. When set, a VTIMEZONE block is added (if missing) and DTSTART/DTEND use TZID instead of UTC
`alarm`	object	—	Single reminder in minutes before the event, or null to remove all existing alarms. For multiple reminders use alarms[].
`dtend`	object	—	New end date/time, or null to remove
`rrule`	object	—	New recurrence rule, or null to remove
`alarms`	array	—	Multiple reminders in minutes before the event (e.g. [1440, 60]). Replaces existing alarms; combined with alarm if both are set.
`status`	string	—	New status
`transp`	string	—	New transparency
`dtstart`	string	—	New start date/time (YYYYMMDD or YYYYMMDDTHHmmssZ)
`summary`	string	—	New event title
`location`	object	—	New location, or null to remove
`attendees`	object	—	Replace attendees list, or null to remove all attendees

Parameters from the server's own tool schema.

RISK

Why update_event is rated Medium

The tool modifies existing calendar event data, which is a Write operation—data is changed but can be reverted or corrected. It is not Destructive (no deletion), Execute (no command/code execution), Financial (no money movement), or Read (actively changes state).

From the tool's definition Tool name 'update_event' and description 'Update an existing calendar event's fields' explicitly indicate modification of data. CalDAV ETag-based concurrency control confirms reversible updates rather than deletion.

Risk signalsHigh parameter count (16 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_event, this is the rule to start with:

update_event Rate-limited

update_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": {
    "update_event": {
      "limits": [
        {
          "counter": "update_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 update_event call is checked against it from then on.

FAQ

Questions about update_event

What does the update_event tool do? +

Update an existing calendar event's fields by UID. Uses CalDAV ETag-based optimistic concurrency. 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 update_event accept? +

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

How do I enforce a policy on update_event? +

Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for update_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 update_event? +

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

Can I rate-limit update_event? +

Yes. Add a rate_limit block to the update_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 update_event completely? +

Set action: deny in the PolicyLayer policy for update_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 update_event? +

update_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

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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