List calendar events in a time range. Returns events in TOON or JSON format.
AI agents call list_events 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 time range (RFC 3339 datetime string). |
query | string | null | — | Optional search query to filter events by summary or description keyword (case-insensitive). |
start | string | Yes | Start of the time range (RFC 3339 datetime string). |
format | string | null | — | Output format: "toon" or "json" (default: "json"). |
calendar_id | string | Yes | Calendar ID to list events from. |
Parameters from the server's own tool schema.
Even though list_events 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.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
List calendar events in a time range. Returns events in TOON or JSON format. It is categorised as a Read tool in the Temporal Cortex Calendar MCP MCP Server, which means it retrieves data without modifying state.
list_events accepts 5 parameters: end, query, start, format, calendar_id. Required: end, start, 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 list_events: 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.
list_events 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 list_events 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 list_events. 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.
list_events 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.