Low Risk

calendar_v3_freebusy_query

[Calendar API v3] Query free/busy information for calendars

Part of the Google Calendar and Meet MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call calendar_v3_freebusy_query to retrieve information from Google Calendar and Meet without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though calendar_v3_freebusy_query only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

inside-hair-mcp-google-meet-and-calendar.yaml
tools:
  calendar_v3_freebusy_query:
    rules:
      - action: allow

See the full Google Calendar and Meet policy for all 25 tools.

Tool Name calendar_v3_freebusy_query
Category Read
Risk Level Low

View all 25 tools →

Agents calling read-class tools like calendar_v3_freebusy_query have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the calendar_v3_freebusy_query tool do? +

[Calendar API v3] Query free/busy information for calendars. It is categorised as a Read tool in the Google Calendar and Meet MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on calendar_v3_freebusy_query? +

Add a rule in your Intercept YAML policy under the tools section for calendar_v3_freebusy_query. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Calendar and Meet MCP server.

What risk level is calendar_v3_freebusy_query? +

calendar_v3_freebusy_query is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit calendar_v3_freebusy_query? +

Yes. Add a rate_limit block to the calendar_v3_freebusy_query rule in your Intercept 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.

How do I block calendar_v3_freebusy_query completely? +

Set action: deny in the Intercept policy for calendar_v3_freebusy_query. 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.

What MCP server provides calendar_v3_freebusy_query? +

calendar_v3_freebusy_query is provided by the Google Calendar and Meet MCP server (INSIDE-HAIR/mcp-google-meet-and-calendar). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Google Calendar and Meet

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.