Find free time slots across specified calendars
AI agents call calendar_findFreeTime to retrieve information from Google MCP Remote 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 calendar data to identify available time periods. It has no side effects—it does not create, modify, delete events, execute code, or commit financial obligations. The action is purely informational (read-only), making it a Read category risk with low severity. The confidence is high because the description clearly indicates a data retrieval operation.
From the tool's definition Tool name 'calendar_findFreeTime' and description 'Find free time slots across specified calendars' indicate a query/search operation that retrieves calendar availability data without modifying, executing external actions, or triggering financial transactions.
Documented attack patterns abuse exactly the kind of access calendar_findFreeTime gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google MCP Remote, and nothing reaches the server without passing your rules. This is the rule we recommend for calendar_findFreeTime:
{
"version": "1",
"default": "deny",
"tools": {
"calendar_findFreeTime": {}
}
} calendar_findFreeTime 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 free time slots across specified calendars. It is categorised as a Read tool in the Google MCP Remote MCP Server, which means it retrieves data without modifying state.
Register the Google MCP Remote MCP server in PolicyLayer and add a rule for calendar_findFreeTime: 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 Remote. Nothing to install.
calendar_findFreeTime 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_findFreeTime 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_findFreeTime. 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_findFreeTime is provided by the Google MCP Remote MCP server (vakharwalad23/google-mcp-remote). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google MCP Remote, 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 Remote tools catalogued and risk-classified — across an index of 43,000+ MCP servers.