Find available time slots in the calendar
AI agents call find_free_time to retrieve information from Google Calendar MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries calendar state to determine availability, analogous to a search or filter operation. It has no side effects—no events are created, modified, or deleted. Even though the sibling tools on this server include destructive capabilities (delete_event, create_event, update_event), this specific tool is purely informational.
From the tool's definition Tool name 'find_free_time' and description 'Find available time slots in the calendar' indicate a query operation that retrieves calendar availability data without modifying or deleting anything.
Documented attack patterns abuse exactly the kind of access find_free_time gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Calendar MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for find_free_time:
{
"version": "1",
"default": "deny",
"tools": {
"find_free_time": {}
}
}find_free_time 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.
Find available time slots in the calendar. It is categorised as a Read tool in the Google Calendar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Calendar MCP Server MCP server in PolicyLayer and add a rule for find_free_time: 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 Calendar MCP Server. Nothing to install.
find_free_time 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 find_free_time 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 find_free_time. 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.
find_free_time is provided by the Google Calendar MCP Server MCP server (v-3/google-calendar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Google Calendar MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Google Calendar MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.