Query free/busy information for calendars
AI agents call get-freebusy 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.
This tool retrieves calendar availability information without creating, modifying, deleting, or executing any operations. It is purely informational, making it a Read operation with low severity since exposure of free/busy data has minimal blast radius—it reveals scheduling information but cannot be used to alter calendar state, delete events, or commit financial transactions.
From the tool's definition Tool name is 'get-freebusy' and description states 'Query free/busy information for calendars'. The verb 'Query' and the action of retrieving free/busy status indicates data retrieval with no modifications or side effects.
Attacks that exploit this kind of access
Query free/busy information for calendars. 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 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 Google Calendar MCP Server. 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 Google Calendar MCP Server MCP server (progrmoiz/cal-mcp). 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 →