list_events
Lists events on a calendar: id, summary, start/end (all-day events carry date with an EXCLUSIVE end; timed events carry dateTime), status, attendees with responseStatus, organizer, recurrence, hangoutLink, eventType. time_min/time_max bound the window (an event overlapping the window is included)...
This record as markdown: /tools/a1-x-tech-mcp-google-calendar/list-events.md
What list_events does on Mcp Google Calendar
AI agents call list_events to retrieve information from Mcp Google Calendar without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | — | Free-text search over summary, description, location and attendees. |
order_by | string | — | Sort order; start_time works only with single_events=true. Default is unspecified order. |
time_max | string | — | Only events starting before this RFC3339 moment (window upper bound, exclusive). |
time_min | string | — | Only events ending at/after this RFC3339 moment (window lower bound). |
time_zone | string | — | IANA zone the response times are rendered in (defaults to the calendar's zone). |
page_token | string | — | nextPageToken from the previous page. |
calendar_id | string | Yes | The calendar id from list_calendars, or "primary" for the authenticated user's main calendar. |
event_types | array | — | Only these event types (e.g. ["out_of_office"] to see OOO blocks). |
max_results | integer | — | Max events per page (1..2500; API default 250). |
updated_min | string | — | Only events modified after this RFC3339 moment — for incremental polling; too-old values return HTTP 410. |
show_deleted | boolean | — | Include cancelled events (status=cancelled). |
single_events | boolean | — | Expand recurring events into instances (required for order_by=start_time). |
Parameters from the server's own tool schema.
Why list_events is rated Low
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 signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs list_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Google Calendar, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_events, this is the rule to start with:
list_events is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Google Calendar, apply this rule, and every list_events call is checked against it from then on.
Questions about list_events
Lists events on a calendar: id, summary, start/end (all-day events carry date with an EXCLUSIVE end; timed events carry dateTime), status, attendees with responseStatus, organizer, recurrence, hangoutLink, eventType. time_min/time_max bound the window (an event overlapping the window is included). single_events=true expands recurring events into individual instances — required for order_by=start_time and the right choice for questions like "what is on my calendar this week"; without it recurring events appear once as the series master. time_zone only changes how times are RENDERED in the response, never the events themselves. q searches summary/description/location/attendees. updated_min + show_deleted enable incremental polling (cancelled events come back as status=cancelled). Paginate with page_token from nextPageToken. It is categorised as a Read tool in the Mcp Google Calendar MCP Server, which means it retrieves data without modifying state.
list_events accepts 12 parameters: q, order_by, time_max, time_min, time_zone, page_token, calendar_id, event_types, max_results, updated_min, show_deleted, single_events. Required: calendar_id. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Google 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 Mcp Google Calendar. 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 Mcp Google Calendar MCP server (@a1-x-tech/mcp-google-calendar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Google Calendar, and thousands of servers like it.
This server
Across the catalogue