list_calendars
Lists the calendars on the user's calendar list: id (use it as calendar_id in every other tool), summary, description, timeZone (IANA), accessRole (owner/writer/reader/freeBusyReader — writes need writer or owner), primary:true on the main calendar, and hidden/selected flags. The special id "prim...
This record as markdown: /tools/a1-x-tech-mcp-google-calendar/list-calendars.md
What list_calendars does on Mcp Google Calendar
AI agents call list_calendars 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 |
|---|---|---|---|
page_token | string | — | nextPageToken from the previous page. |
max_results | integer | — | Max calendars per page (1..250; API default 100). |
show_hidden | boolean | — | Include calendars the user has hidden from their list. |
min_access_role | string | — | Only calendars where the user has at least this role (e.g. writer to find writable ones). |
Parameters from the server's own tool schema.
Why list_calendars is rated Low
Even though list_calendars 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs list_calendars 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_calendars, this is the rule to start with:
list_calendars 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_calendars call is checked against it from then on.
Questions about list_calendars
Lists the calendars on the user's calendar list: id (use it as calendar_id in every other tool), summary, description, timeZone (IANA), accessRole (owner/writer/reader/freeBusyReader — writes need writer or owner), primary:true on the main calendar, and hidden/selected flags. The special id "primary" always addresses the main calendar without listing first. Paginate with page_token from nextPageToken. Calendars shared with the user but never added to their list do not appear here — address them by their explicit id. It is categorised as a Read tool in the Mcp Google Calendar MCP Server, which means it retrieves data without modifying state.
list_calendars accepts 4 parameters: page_token, max_results, show_hidden, min_access_role. 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_calendars: 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_calendars 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_calendars 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_calendars. 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_calendars 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