icloud-calendar_update_event · Icloud MCP: Risk & Policy

WHAT IT DOES

What icloud-calendar_update_event does on Icloud

AI agents use icloud-calendar_update_event to create or update resources in Icloud — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Icloud environment.

WHY IT NEEDS A POLICY

Why icloud-calendar_update_event needs a policy

This tool creates or modifies data in a reversible manner (calendar event metadata/scheduling). While calendar updates are not destructive, they do change user-facing data. The severity is medium because misuse could disrupt a user's schedule or cause calendar conflicts, but the effects are recoverable (events can be re-updated or restored from backups).

From the tool's definition Tool description states 'Updates an existing iCloud calendar event', which modifies data reversibly. The term 'update' is a classic Write operation. The tool operates on calendar events, a user-facing data structure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

icloud-calendar_update_event Rate-limited

icloud-calendar_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": {
    "icloud-calendar_update_event": {
      "limits": [
        {
          "counter": "icloud-calendar_update_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Icloud, so you can run agents against it safely.

FAQ

Questions about icloud-calendar_update_event

What does the icloud-calendar_update_event tool do? +

Updates an existing iCloud calendar event by its CalDAV URL. It is categorised as a Write tool in the Icloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on icloud-calendar_update_event? +

Register the Icloud MCP server in PolicyLayer and add a rule for icloud-calendar_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 Icloud. Nothing to install.

What risk level is icloud-calendar_update_event? +

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

Can I rate-limit icloud-calendar_update_event? +

Yes. Add a rate_limit block to the icloud-calendar_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 icloud-calendar_update_event completely? +

Set action: deny in the PolicyLayer policy for icloud-calendar_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 icloud-calendar_update_event? +

icloud-calendar_update_event is provided by the Icloud MCP server (thefredlab/icloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.