calendar_list_events
List events from Google Calendar. Shows upcoming events by default. Can filter by date range and search query.
This record as markdown: /tools/io-github-saloprj-dialogbrain/calendar-list-events.md
What calendar_list_events does on Dialogbrain
AI agents call calendar_list_events to retrieve information from Dialogbrain 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 query to filter events. |
date_to | string | — | End date/time to query (YYYY-MM-DD or ISO 8601 format). Defaults to 7 days from now. Alias: time_max. |
date_from | string | — | Start date/time to query (YYYY-MM-DD or ISO 8601 format). Defaults to now. Alias: time_min. |
calendar_id | string | — | Calendar ID to list events from. OMIT to use the agent's configured default calendar (or primary). |
max_results | integer | — | Maximum number of events to return. |
Parameters from the server's own tool schema.
Why calendar_list_events is rated Low
The tool retrieves calendar event data without any side effects. Filtering and searching are read operations. There is no capability to create, modify, delete, or execute actions based on calendar data. The blast radius of misuse is minimal—an AI agent could only access calendar information it's authorized to view.
From the tool's definition Tool name contains 'list', description states 'List events from Google Calendar' and 'Shows upcoming events by default.
Attacks that exploit this kind of access
The rule that runs calendar_list_events safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For calendar_list_events, this is the rule to start with:
calendar_list_events 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 Dialogbrain, apply this rule, and every calendar_list_events call is checked against it from then on.
Questions about calendar_list_events
List events from Google Calendar. Shows upcoming events by default. Can filter by date range and search query. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
calendar_list_events accepts 5 parameters: query, date_to, date_from, calendar_id, max_results. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for calendar_list_events: 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 Dialogbrain. Nothing to install.
calendar_list_events 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 calendar_list_events 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 calendar_list_events. 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.
calendar_list_events is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue