Find available time slots between events
AI agents call google_calendar_find_free_time to retrieve information from Google MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and analyzes existing calendar data to identify gaps between events. It is a read-only operation with no side effects—it does not create, modify, delete, or execute actions. The blast radius of misuse is minimal; an agent querying free time slots cannot cause harm beyond potentially seeing calendar availability.
From the tool's definition The tool 'google_calendar_find_free_time' with description 'Find available time slots between events' performs a query operation that retrieves scheduling information without modifying or deleting any data.
Documented attack patterns abuse exactly the kind of access google_calendar_find_free_time gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for google_calendar_find_free_time:
{
"version": "1",
"default": "deny",
"tools": {
"google_calendar_find_free_time": {}
}
} google_calendar_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 between events. It is categorised as a Read tool in the Google MCP MCP Server, which means it retrieves data without modifying state.
Register the Google MCP server in PolicyLayer and add a rule for google_calendar_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 MCP. Nothing to install.
google_calendar_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 google_calendar_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 google_calendar_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.
google_calendar_find_free_time is provided by the Google MCP server (vakharwalad23/google-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google MCP, 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.
35 Google MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.