listCalendars
List all accessible Google Calendars for the authenticated user
This record as markdown: /tools/ark7-google-drive-mcp/listcalendars.md
What listCalendars does on Google Drive
AI agents call listCalendars to retrieve information from Google Drive 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 |
|---|---|---|---|
account | string | — | Alias of the Google account to target. Optional — defaults to the session/global default account, or the sole authenticated account. Run manage_accounts list to |
showHidden | boolean | — | Include hidden calendars (default: false) |
Parameters from the server's own tool schema.
Why listCalendars is rated Low
This tool only queries and returns a list of calendars accessible to the user. It performs no writes, deletions, executions, or financial operations. The blast radius if misused by an AI agent is minimal—the user's calendar metadata would be enumerated but not altered. Classification as Read is appropriate.
From the tool's definition Tool name 'listCalendars' and description 'List all accessible Google Calendars' indicate a retrieval operation with no modification of data or side effects.
Attacks that exploit this kind of access
The rule that runs listCalendars safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Drive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For listCalendars, this is the rule to start with:
listCalendars 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 Google Drive, apply this rule, and every listCalendars call is checked against it from then on.
Questions about listCalendars
List all accessible Google Calendars for the authenticated user. It is categorised as a Read tool in the Google Drive MCP Server, which means it retrieves data without modifying state.
listCalendars accepts 2 parameters: account, showHidden. The full parameter table on this page comes from the server's own tool schema.
Register the Google Drive MCP server in PolicyLayer and add a rule for listCalendars: 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 Google Drive. Nothing to install.
listCalendars 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 listCalendars 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 listCalendars. 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.
listCalendars is provided by the Google Drive MCP server (@ark7/google-drive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Drive, and thousands of servers like it.
This server
Across the catalogue