AI agents call calendar_get_free_busy_info to retrieve information from Google 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 status (free/busy times) for specified calendars. It only retrieves existing data without creating, modifying, or deleting anything. The operation is read-only with minimal blast radius if misused — an agent could discover when users are busy, but cannot alter calendars or commit actions. Low severity appropriate for information disclosure only.
From the tool's definition Tool name contains 'get' and description states 'Check free/busy information' — a pure retrieval operation with no modification, deletion, or side effects.
Attacks that exploit this kind of access
Check free/busy information for calendars (comma-separated calendar IDs). It is categorised as a Read tool in the Google MCP Server, which means it retrieves data without modifying state.
Register the Google MCP server in PolicyLayer and add a rule for calendar_get_free_busy_info: 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. Nothing to install.
calendar_get_free_busy_info 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_get_free_busy_info 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_get_free_busy_info. 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_get_free_busy_info is provided by the Google MCP server (robcerda/google-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →