Temporal Cortex Calendar MCP

18 tools. 5 can modify or destroy data without limits.

5 write tools that can modify data. Rate limits recommended.

Last updated:

5 can modify or destroy data
13 read-only
18 tools total

Verified server · catalogue entry verified 28/06/2026 · full schemas captured for 18 of 18 tools

How to control Temporal Cortex Calendar MCP ↓

What Temporal Cortex Calendar MCP exposes to your agents

Read (13) Write / Execute (5) Destructive / Financial (0)

What Temporal Cortex Calendar MCP costs in tokens

3,240 tokens of tool definitions, loaded on every request
1.6% of a 200k context window
386 heaviest tool: compose_proposal
High Risk

The most dangerous Temporal Cortex Calendar MCP tools

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

How to control Temporal Cortex Calendar MCP

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

Rate limit write operations
{
  "compose_proposal": {
    "limits": [
      {
        "counter": "compose_proposal_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "adjust_timestamp": {
    "limits": [
      {
        "counter": "adjust_timestamp_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register Temporal Cortex Calendar MCP — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON TEMPORAL CORTEX CALENDAR →

Instant setup, no code required.

All 18 Temporal Cortex Calendar MCP tools

READ 13 tools
Read adjust_timestamp Adjust a timestamp by adding or subtracting a duration. DST-aware: '+1d' preserves wall-clock time across dayl Read book_slot Book a calendar slot using Two-Phase Commit for safe, conflict-free booking. Read check_availability Check if a calendar time slot is available (not held by another booking). Read compute_duration Compute the duration between two timestamps. Returns days, hours, minutes, seconds, and a human-readable strin Read expand_rrule Expand a recurrence rule (RRULE) into concrete event instances. Read find_free_slots Find available free time slots in a calendar within a time window. Read get_availability Get unified availability across multiple calendars. Merges events from all specified calendars into a single b Read get_temporal_context Get the current temporal context — time, timezone, calendar metadata. Call this first to orient yourself in ti Read list_calendars List all connected calendars across providers. Returns calendar IDs, names, labels, and metadata. Call this fi Read list_events List calendar events in a time range. Returns events in TOON or JSON format. Read query_public_availability Query another user's public availability by their Temporal Link slug. Returns available time slots for a given Read request_booking Book a meeting on another user's public calendar by their Temporal Link slug. Requires attendee_email. Content Read search_contacts Search your contacts by name. Returns matching contacts with emails, phone numbers, organization, and job titl

Questions about Temporal Cortex Calendar MCP

How do I prevent bulk modifications through Temporal Cortex Calendar MCP? +

The Temporal Cortex Calendar MCP server has 5 write tools including compose_proposal, convert_timezone, resolve_contact. 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 Temporal Cortex Calendar MCP.

How many tools does the Temporal Cortex Calendar MCP server expose? +

18 tools across 2 categories: Read, Write. 13 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Temporal Cortex Calendar MCP? +

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

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

Instant setup, no code required.

18 Temporal Cortex Calendar MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.