calendar_check_availability
Check when you have free time in Google Calendar. Shows busy periods and free slots in a given time range. Useful for finding meeting times or checking schedule conflicts.
This record as markdown: /tools/io-github-saloprj-dialogbrain/calendar-check-availability.md
What calendar_check_availability does on Dialogbrain
AI agents call calendar_check_availability 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 |
|---|---|---|---|
end_time | string | — | End date/time to check availability (YYYY-MM-DD or ISO 8601). Defaults to end of start_time day, or 7 days from now. |
start_time | string | — | Start date/time to check availability (YYYY-MM-DD or ISO 8601). Defaults to start of today. |
calendar_id | string | — | Calendar ID to check. OMIT to use the agent's configured default calendar (or primary). |
working_hours_only | boolean | — | If true, only show free slots during working hours (9 AM - 6 PM). OMIT to show all free time (the default). |
min_duration_minutes | integer | — | Minimum duration in minutes for free slots. Filters out short gaps. Default: 30 minutes. |
Parameters from the server's own tool schema.
Why calendar_check_availability is rated Low
Even though calendar_check_availability 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.
Attacks that exploit this kind of access
The rule that runs calendar_check_availability 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_check_availability, this is the rule to start with:
calendar_check_availability 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_check_availability call is checked against it from then on.
Questions about calendar_check_availability
Check when you have free time in Google Calendar. Shows busy periods and free slots in a given time range. Useful for finding meeting times or checking schedule conflicts. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
calendar_check_availability accepts 5 parameters: end_time, start_time, calendar_id, working_hours_only, min_duration_minutes. 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_check_availability: 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_check_availability 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_check_availability 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_check_availability. 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_check_availability 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