// SCAN REPORT

Apple Calendar MCP

22 tools. 6 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

6 can modify or destroy data

16 read-only

22 tools total

Community server · catalogue entry verified 29/06/2026

How to control Apple Calendar MCP ↓

TOOL MAP

What Apple Calendar MCP exposes to your agents

Read (16) Write / Execute (4) Destructive / Financial (2)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Apple Calendar MCP tools

Destructive · Critical revert_character_reminders Find every event in the window whose notes contain the backup sentinel, restore the original title/notes/location, and remove the backup blo Destructive · High delete_event Delete an event by its event_id (uid). Write · Medium apply_character_reminders Mutate calendar event titles using Claude-composed Write · Medium create_event Create a new calendar event. calendar_name defaults to the first writable calendar.

6 of Apple Calendar MCP's 22 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Apple Calendar MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Calendar MCP, 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

{
  "apply_character_reminders": {
    "limits": [
      {
        "counter": "apply_character_reminders_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "cache_research_facts": {
    "limits": [
      {
        "counter": "cache_research_facts_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 Apple Calendar MCP — 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 APPLE CALENDAR →

Instant setup, no code required.

FULL CATALOGUE

All 22 Apple Calendar MCP tools

DESTRUCTIVE 2 tools

Destructive delete_event Delete an event by its event_id (uid). Destructive revert_character_reminders Find every event in the window whose notes contain the backup sentinel, restore the original title/notes/locat

WRITE 4 tools

Write apply_character_reminders Mutate calendar event titles using Claude-composed Write create_event Create a new calendar event. calendar_name defaults to the first writable calendar. Write update_event Update fields of an existing event identified by event_id (its uid). Only provided fields are changed. Write update_memory_from_input Stage 3. Bulk-merges extraction results + research into memory

READ 16 tools

Read cache_research_facts Stage 2 follow-up. Persists Claude Read distill_voice_from_text Take a corpus of someone Read enrich_with_character_reminders List events in a window and attach a relational character (Mom, Friend, Coach, Past-you, etc.) plus per-event Read extract_entities_from_input Stage 1 of YAPPING pipeline. Returns a structured extraction schema instructing Claude to parse a screenshot/m Read list_calendars List all calendars available in macOS Calendar.app, including whether each is writable. Read list_distillers List built-in distillers (synthetic voices distilled from public material — Garry Tan, PG, Naval, Karpathy, St Read list_events List events in Calendar.app between start_date and end_date (ISO 8601). Optionally filter by calendar. Read list_events_in_mixed_personas Wraps list_events and assigns a distinct voice from a 30+ pool to each event (no two events share a voice). Op Read list_events_in_persona List events between start_date and end_date and return them alongside a persona directive that Read mortality_overlay Wraps list_events and attaches a per-event life_percent_consumed (and cumulative running total) so callers can Read query_calendar_memory Read seeded calendar memory by person, topic, date range, calendar, similarity to a synthetic event, or all. R Read query_full_context_for_event Stage 6. Returns the full context bundle (memory + people + topics + external facts + user notes) for one even Read research_entities Stage 2. Returns cached external_facts plus a research directive for entities not yet known. Claude does web s Read search_events Search events by substring match against title, location, and notes (case-insensitive). Defaults to 30 days ag Read seed_calendar_memory Snapshot past events from writable calendars into ~/.apple-calendar-mcp/memory.json so character reminders can Read time_per_calendar Aggregate event durations per calendar within a time window. Returns timed seconds, event counts,

EXPLORE

Related servers

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

FAQ

Questions about Apple Calendar MCP

Can an AI agent delete data through the Apple Calendar MCP server? +

Yes. The Apple Calendar MCP server exposes 2 destructive tools including delete_event, revert_character_reminders. 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 Apple Calendar MCP? +

The Apple Calendar MCP server has 4 write tools including apply_character_reminders, 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 Apple Calendar MCP.

How many tools does the Apple Calendar MCP server expose? +

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

How do I enforce a policy on Apple Calendar MCP? +

Register the Apple Calendar 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 Apple Calendar MCP tool call.

Deterministic rules across all 22 Apple Calendar MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON APPLE CALENDAR →

Instant setup, no code required.

22 Apple Calendar MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.