Synchronizes Google Calendar events, performing a full sync if no `sync_token` is provided or if a 410 GONE error (due to an expired token) necessitates it, otherwise performs an incremental sync for events changed since the `sync_token` was issued.
Part of the Google Calendar MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call GOOGLECALENDAR_SYNC_EVENTS to retrieve information from Google Calendar 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 GOOGLECALENDAR_SYNC_EVENTS 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.
tools:
GOOGLECALENDAR_SYNC_EVENTS:
rules:
- action: allowSee the full Google Calendar policy for all 29 tools.
Agents calling read-class tools like GOOGLECALENDAR_SYNC_EVENTS have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Synchronizes Google Calendar events, performing a full sync if no `sync_token` is provided or if a 410 GONE error (due to an expired token) necessitates it, otherwise performs an incremental sync for events changed since the `sync_token` was issued.. It is categorised as a Read tool in the Google Calendar MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for GOOGLECALENDAR_SYNC_EVENTS. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Calendar MCP server.
GOOGLECALENDAR_SYNC_EVENTS 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 GOOGLECALENDAR_SYNC_EVENTS 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.
Set action: deny in the Intercept policy for GOOGLECALENDAR_SYNC_EVENTS. 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.
GOOGLECALENDAR_SYNC_EVENTS is provided by the Google Calendar MCP server (google-cal-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept