get-freebusy
Check calendar availability. Returns: busy time blocks per calendar. Use when: finding available slots, scheduling across calendars. Note: only shows busy/free, not event details.
This record as markdown: /tools/199-biotechnologies-mcp-google/get-freebusy.md
What get-freebusy does on MCP Google Workspace
AI agents call get-freebusy to retrieve information from MCP Google Workspace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-freebusy is rated Low
This tool queries calendar data to retrieve availability information. It performs a pure read operation with no side effects—it neither creates, modifies, deletes, executes code, nor involves financial transactions. The restricted output (busy/free blocks only, not full event details) further confirms it is a safe, informational query.
From the tool's definition Tool name 'get-freebusy' and description states it 'Check calendar availability' and 'Returns: busy time blocks per calendar'. Explicitly notes 'only shows busy/free, not event details', indicating retrieval without modification.
Attacks that exploit this kind of access
The rule that runs get-freebusy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Google Workspace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-freebusy, this is the rule to start with:
get-freebusy is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Google Workspace, apply this rule, and every get-freebusy call is checked against it from then on.
Questions about get-freebusy
Check calendar availability. Returns: busy time blocks per calendar. Use when: finding available slots, scheduling across calendars. Note: only shows busy/free, not event details. It is categorised as a Read tool in the MCP Google Workspace MCP Server, which means it retrieves data without modifying state.
Register the MCP Google Workspace MCP server in PolicyLayer and add a rule for get-freebusy: 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 MCP Google Workspace. Nothing to install.
get-freebusy 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 get-freebusy 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 get-freebusy. 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.
get-freebusy is provided by the MCP Google Workspace MCP server (199-mcp/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Google Workspace, and thousands of servers like it.
This server
Across the catalogue