getCalendarEvents
Get events from a Google Calendar with optional filtering
This record as markdown: /tools/ark7-google-drive-mcp/getcalendarevents.md
What getCalendarEvents does on Google Drive
AI agents call getCalendarEvents 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 |
|---|---|---|---|
query | string | — | Free text search in events |
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 |
orderBy | string | — | Sort order (default: startTime) |
timeMax | string | — | End of time range (RFC3339) |
timeMin | string | — | Start of time range (RFC3339, e.g., '2024-01-01T00:00:00Z') |
calendarId | string | — | Calendar ID (default: primary) |
maxResults | number | — | Maximum events to return (1-250, default: 50) |
singleEvents | boolean | — | Expand recurring events into instances (default: true) |
Parameters from the server's own tool schema.
Why getCalendarEvents is rated Low
This tool retrieves calendar event data without modifying, executing, or destroying anything. It is a straightforward read operation that queries existing calendar events with optional filters. The blast radius of misuse is minimal—an AI agent could potentially access calendar information it shouldn't, but cannot cause damage or irreversible changes.
From the tool's definition Tool name 'getCalendarEvents' and description 'Get events from a Google Calendar with optional filtering' indicate retrieval and querying operations only, with no modification, execution, or deletion of data.
Attacks that exploit this kind of access
The rule that runs getCalendarEvents 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 getCalendarEvents, this is the rule to start with:
getCalendarEvents 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 getCalendarEvents call is checked against it from then on.
Questions about getCalendarEvents
Get events from a Google Calendar with optional filtering. It is categorised as a Read tool in the Google Drive MCP Server, which means it retrieves data without modifying state.
getCalendarEvents accepts 8 parameters: query, account, orderBy, timeMax, timeMin, calendarId, maxResults, singleEvents. 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 getCalendarEvents: 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.
getCalendarEvents 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 getCalendarEvents 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 getCalendarEvents. 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.
getCalendarEvents 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