calendar_acl_watch

Subscribe to changes on calendar ACL

Part of the Google Workspace Calendar (gws CLI) MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@gws mcp -s calendar Read Risk 3/5

// WHEN AI AGENTS USE THIS TOOL

AI agents call calendar_acl_watch to retrieve information from Google Workspace Calendar (gws CLI) 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.

// WHY ENFORCE A POLICY ON CALENDAR_ACL_WATCH

Even though calendar_acl_watch 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.

// RECOMMENDED POLICY

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

google-workspace-calendar.yaml

tools:
  calendar_acl_watch:
    rules:
      - action: allow

See the full Google Workspace Calendar (gws CLI) policy for all 37 tools.

// DETAILS

Tool Name calendar_acl_watch

Category Read

MCP Server Google Workspace Calendar (gws CLI) MCP Server

Risk Level Low

// MORE GOOGLE WORKSPACE CALENDAR (GWS CLI) TOOLS

Destructive calendar_acl_delete Destructive calendar_calendarList_delete Destructive calendar_calendars_clear Destructive calendar_calendars_delete Destructive calendar_events_delete Execute calendar_channels_stop Write calendar_acl_insert Write calendar_acl_patch

View all 37 tools →

// WHAT CAN GO WRONG

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

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

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

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the calendar_acl_watch tool do? +

Subscribe to changes on calendar ACL. It is categorised as a Read tool in the Google Workspace Calendar (gws CLI) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on calendar_acl_watch? +

Add a rule in your Intercept YAML policy under the tools section for calendar_acl_watch. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Workspace Calendar (gws CLI) MCP server.

What risk level is calendar_acl_watch? +

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

Can I rate-limit calendar_acl_watch? +

Yes. Add a rate_limit block to the calendar_acl_watch 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_acl_watch completely? +

Set action: deny in the Intercept policy for calendar_acl_watch. 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_acl_watch? +

calendar_acl_watch is provided by the Google Workspace Calendar (gws CLI) MCP server (@gws mcp -s calendar). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

calendar_acl_watch

Enforce policies on Google Workspace Calendar (gws CLI)