# 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.

Agent View of the PolicyLayer registry record for `list_events`. HTML page: https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/list-events

## Facts

- Tool: `list_events`
- Server: Mcp Google Calendar (`@a1-x-tech/mcp-google-calendar`) — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar.md
- Install: `npx -y @a1-x-tech/mcp-google-calendar`
- Homepage: https://github.com/A1-x-Tech/mcp-google-calendar
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 12 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `q` | string | no | Free-text search over summary, description, location and attendees. |
| `order_by` | string | no | Sort order; start_time works only with single_events=true. Default is unspecified order. |
| `time_max` | string | no | Only events starting before this RFC3339 moment (window upper bound, exclusive). |
| `time_min` | string | no | Only events ending at/after this RFC3339 moment (window lower bound). |
| `time_zone` | string | no | IANA zone the response times are rendered in (defaults to the calendar's zone). |
| `page_token` | string | no | 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 | no | Only these event types (e.g. ["out_of_office"] to see OOO blocks). |
| `max_results` | integer | no | Max events per page (1..2500; API default 250). |
| `updated_min` | string | no | Only events modified after this RFC3339 moment — for incremental polling; too-old values return HTTP 410. |
| `show_deleted` | boolean | no | Include cancelled events (status=cancelled). |
| `single_events` | boolean | no | Expand recurring events into instances (required for order_by=start_time). |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_events",
    "arguments": {
      "calendar_id": "<calendar_id>"
    }
  }
}
```

## 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 signals: High parameter count (12 properties)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Google Calendar:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_events": {}
  }
}
```

## Other tools on Mcp Google Calendar (18)

- `delete_event` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/delete-event.md
- `logout` — Destructive — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/logout.md
- `start_login` — Execute — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/start-login.md
- `auth_status` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/auth-status.md
- `get_calendar` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/get-calendar.md
- `get_event` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/get-event.md
- `list_calendars` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/list-calendars.md
- `list_event_instances` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/list-event-instances.md
- `query_free_busy` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/query-free-busy.md
- `raw_request` — Read — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/raw-request.md
- `create_event` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/create-event.md
- `create_focus_time` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/create-focus-time.md
- `create_out_of_office` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/create-out-of-office.md
- `finish_login` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/finish-login.md
- `move_event` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/move-event.md
- `set_client` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/set-client.md
- `setup_instructions` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/setup-instructions.md
- `update_event` — Write — https://policylayer.com/tools/a1-x-tech-mcp-google-calendar/update-event.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=a1-x-tech-mcp-google-calendar · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/a1-x-tech-mcp-google-calendar