// SCAN REPORT

iCloud CalDAV MCP Connector

8 tools. 3 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 30 Jun 2026

3 can modify or destroy data

5 read-only

8 tools total

Community server · catalogue entry verified 30/06/2026

How to control iCloud CalDAV MCP Connector ↓

TOOL MAP

What iCloud CalDAV MCP Connector exposes to your agents

Read (5) Write / Execute (2) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous iCloud CalDAV MCP Connector tools

Destructive · High delete_event This tool permanently removes calendar events without possibility of reversal. Write · Medium create_event Creating calendar events is a reversible modification action—events can be updated or deleted later. Write · Medium update_event This tool modifies existing calendar data reversibly.

3 of iCloud CalDAV MCP Connector's 8 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control iCloud CalDAV MCP Connector

PolicyLayer is an MCP gateway — it sits between your AI agents and iCloud CalDAV MCP Connector, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_event": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_event": {
    "limits": [
      {
        "counter": "create_event_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "fetch": {
    "limits": [
      {
        "counter": "fetch_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register iCloud CalDAV MCP Connector — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ICLOUD CALDAV MCP CONNECTOR →

Instant setup, no code required.

FULL CATALOGUE

All 8 iCloud CalDAV MCP Connector tools

DESTRUCTIVE 1 tools

Destructive delete_event Delete a VEVENT by UID from the given calendar.

WRITE 2 tools

Write create_event create_event Write update_event Update a VEVENT identified by UID.

READ 5 tools

Read fetch Fetch raw ICS for ids returned by search(). Read list_calendars Return available calendar containers with their name and URL. Read list_calendars_with_events Return calendars that have at least one event between ISO datetimes Read list_events List events between ISO datetimes [start, end). Read search Read-only search across SUMMARY and DESCRIPTION within a time window.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about iCloud CalDAV MCP Connector

Can an AI agent delete data through the iCloud CalDAV MCP Connector MCP server? +

Yes. The iCloud CalDAV MCP Connector server exposes 1 destructive tools including delete_event. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through iCloud CalDAV MCP Connector? +

The iCloud CalDAV MCP Connector server has 2 write tools including create_event, update_event. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach iCloud CalDAV MCP Connector.

How many tools does the iCloud CalDAV MCP Connector MCP server expose? +

8 tools across 3 categories: Destructive, Read, Write. 5 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on iCloud CalDAV MCP Connector? +

Register the iCloud CalDAV MCP Connector MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every iCloud CalDAV MCP Connector tool call.

Deterministic rules across all 8 iCloud CalDAV MCP Connector tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ICLOUD CALDAV MCP CONNECTOR →

Instant setup, no code required.

8 iCloud CalDAV MCP Connector tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from iCloud CalDAV MCP Connector's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →