Get unified availability across multiple calendars. Merges events from all specified calendars into a single busy/free view with privacy controls.
AI agents call get_availability 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 of the availability window (RFC 3339 datetime string). |
start | string | Yes | Start of the availability window (RFC 3339 datetime string). |
format | string | null | — | Output format: "toon" (default, token-efficient) or "json". |
privacy | string | null | — | Privacy mode: "opaque" (default) hides source counts, "full" shows them. |
calendar_ids | array | null | — | Calendar IDs to query. If omitted, queries "primary". |
working_hours_only | boolean | null | — | If true, only return free slots within configured working hours (default: false). Uses the tenant's configured working hours (default 09:00–17:00) and timezone. |
min_free_slot_minutes | integer | null | — | Minimum free slot duration in minutes (default: 30). |
Parameters from the server's own tool schema.
Even though get_availability 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
Get unified availability across multiple calendars. Merges events from all specified calendars into a single busy/free view with privacy controls. It is categorised as a Read tool in the Temporal Cortex Calendar MCP MCP Server, which means it retrieves data without modifying state.
get_availability accepts 7 parameters: end, start, format, privacy, calendar_ids, working_hours_only, min_free_slot_minutes. Required: end, start. 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 get_availability: 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.
get_availability 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 get_availability 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 get_availability. 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.
get_availability 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.