Book a calendar slot using Two-Phase Commit for safe, conflict-free booking.
AI agents call book_slot to retrieve information from Temporal Cortex Calendar MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
end | string | Yes | End time for the booking (RFC 3339 datetime string). |
start | string | Yes | Start time for the booking (RFC 3339 datetime string). |
summary | string | Yes | Event summary/title. |
location | string | null | — | Optional meeting location (e.g., "Conference Room A", "https://zoom.us/j/123"). |
attendees | array | null | — | Optional list of attendee email addresses. |
calendar_id | string | Yes | Calendar ID to book in (UUID string). |
description | string | null | — | Optional event description. |
Parameters from the server's own tool schema.
Even though book_slot only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
Book a calendar slot using Two-Phase Commit for safe, conflict-free booking. It is categorised as a Read tool in the Temporal Cortex Calendar MCP MCP Server, which means it retrieves data without modifying state.
book_slot accepts 7 parameters: end, start, summary, location, attendees, calendar_id, description. Required: end, start, summary, calendar_id. The full parameter table on this page comes from the server's own tool schema.
Register the Temporal Cortex Calendar MCP server in PolicyLayer and add a rule for book_slot: 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 Temporal Cortex Calendar MCP. Nothing to install.
book_slot is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the book_slot 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.
Set action: deny in the PolicyLayer policy for book_slot. 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.
book_slot is provided by the Temporal Cortex Calendar MCP server (temporal-cortex/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.