GOOGLESUPER_FIND_EVENT
Finds events in a specified Google Calendar using text query, time ranges (event start/end, last modification), and event types; ensure timeMin is not chronologically after timeMax if both are provided.
This record as markdown: /tools/googlesuper/googlesuper-find-event.md
What GOOGLESUPER_FIND_EVENT does on Google Super
AI agents call GOOGLESUPER_FIND_EVENT to retrieve information from Google Super 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 terms to find events. This query is matched against various event fields including summary, description, location, attendees' details (displayN |
timeMax | string | — | Upper bound (exclusive) for an event's start time to filter by. Only events starting before this time are included. Accepts multiple formats: 1. RFC3339 timesta |
timeMin | string | — | Lower bound (exclusive) for an event's end time to filter by. Only events ending after this time are included. Accepts multiple formats: 1. RFC3339 timestamp (e |
order_by | string | — | Order of events: 'startTime' (ascending by start time) or 'updated' (ascending by last modification time). Note: 'startTime' requires single_events=true. Use 'u |
page_token | string | — | Token from a previous response's `nextPageToken` to fetch the subsequent page of results. |
calendar_id | string | — | Identifier of the Google Calendar to query. Use 'primary' for the primary calendar of the authenticated user, an email address for a specific user's calendar, o |
event_types | array | — | Event types to include. Supported values: 'birthday', 'default', 'focusTime', 'outOfOffice', 'workingLocation'. |
max_results | integer | — | Maximum number of events per page (1-2500). |
updated_min | string | — | Lower bound (exclusive) for an event's last modification time to filter by. Only events updated after this time are included. When specified, events deleted sin |
show_deleted | boolean | — | Include events whose status is 'cancelled'. This surfaces cancelled/deleted events, not a separate 'trash' view. Behavior with recurring events: when single_eve |
single_events | boolean | — | When true, recurring event series are expanded into their individual instances. When false, only the recurring master events are returned. Note: Ordering by 'st |
Parameters from the server's own tool schema.
Why GOOGLESUPER_FIND_EVENT is rated Low
GOOGLESUPER_FIND_EVENT performs read-only retrieval of calendar event data. It accepts search parameters (text query, date ranges) and returns matching events without any side effects. This is a classic Read operation—search/query functionality. The low severity reflects minimal blast radius: an attacker could discover calendar events but cannot modify, delete, or execute actions through this tool alone.
From the tool's definition Tool description states it "Finds events in a specified Google Calendar using text query, time ranges" - these are query and filter operations with no modification, creation, deletion, or execution mentioned.
Risk signalsAccepts freeform code/query input (query) · High parameter count (11 properties)
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_FIND_EVENT safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_FIND_EVENT, this is the rule to start with:
GOOGLESUPER_FIND_EVENT 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 Super, apply this rule, and every GOOGLESUPER_FIND_EVENT call is checked against it from then on.
Questions about GOOGLESUPER_FIND_EVENT
Finds events in a specified Google Calendar using text query, time ranges (event start/end, last modification), and event types; ensure timeMin is not chronologically after timeMax if both are provided. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.
GOOGLESUPER_FIND_EVENT accepts 11 parameters: query, timeMax, timeMin, order_by, page_token, calendar_id, event_types, max_results, updated_min, show_deleted, single_events. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_FIND_EVENT: 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 Super. Nothing to install.
GOOGLESUPER_FIND_EVENT 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 GOOGLESUPER_FIND_EVENT 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 GOOGLESUPER_FIND_EVENT. 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.
GOOGLESUPER_FIND_EVENT is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Google Super, and thousands of servers like it.
This server
Across the catalogue