Check availability (free/busy times) for one or more calendars within a time range. This is useful for finding available meeting times across multiple people. It only returns busy time blocks (not event details) for privacy. Args: - time_min (string): Start of the time range (ISO 8601 format, e.g.,
AI agents call calendar_freebusy_query to retrieve information from Google Workspace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries calendar availability information and returns only aggregated free/busy status without event details, side effects, or data modification. It is a pure read operation with minimal sensitive data exposure due to privacy-preserving aggregation of results. No write, execute, destructive, or financial impact is possible.
From the tool's definition The tool 'Check availability (free/busy times) for one or more calendars' retrieves calendar data without modification. The description explicitly states 'It only returns busy time blocks (not event details) for privacy', indicating data retrieval only.
Documented attack patterns abuse exactly the kind of access calendar_freebusy_query gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Workspace, and nothing reaches the server without passing your rules. This is the rule we recommend for calendar_freebusy_query:
{
"version": "1",
"default": "deny",
"tools": {
"calendar_freebusy_query": {}
}
}calendar_freebusy_query is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check availability (free/busy times) for one or more calendars within a time range. This is useful for finding available meeting times across multiple people. It only returns busy time blocks (not event details) for privacy. Args: - time_min (string): Start of the time range (ISO 8601 format, e.g.,. It is categorised as a Read tool in the Google Workspace MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP server in PolicyLayer and add a rule for calendar_freebusy_query: 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 Workspace. Nothing to install.
calendar_freebusy_query 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_freebusy_query 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_freebusy_query. 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_freebusy_query is provided by the Google Workspace MCP server (everyinc/google-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Workspace, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Google Workspace tools catalogued and risk-classified — across an index of 43,000+ MCP servers.