37 tools. 21 can modify or destroy data without limits.
5 destructive tools with no built-in limits. Policy required.
Last updated:
Destructive tools (calendar_acl_delete, calendar_calendarList_delete, calendar_calendars_clear) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.
Write operations (calendar_acl_insert, calendar_acl_patch, calendar_acl_update) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (calendar_channels_stop) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Google Workspace Calendar (gws CLI). Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.
npx -y @policylayer/intercept scan -- npx -y @gws mcp -s calendar calendar_acl_delete:
rules:
- action: deny Destructive tools should never be available to autonomous agents without human approval.
calendar_acl_insert:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
calendar_acl_get:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Google Workspace Calendar (gws CLI) server exposes 5 destructive tools including calendar_acl_delete, calendar_calendarList_delete, calendar_calendars_clear. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.
The Google Workspace Calendar (gws CLI) server has 15 write tools including calendar_acl_insert, calendar_acl_patch, calendar_acl_update. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.
37 tools across 4 categories: Destructive, Execute, Read, Write. 16 are read-only. 21 can modify, create, or delete data.
One line change. Instead of running the Google Workspace Calendar (gws CLI) server directly, prefix it with Intercept: intercept -c google-workspace-calendar.yaml -- npx -y @@gws mcp -s calendar. Download a pre-built policy from policylayer.com/policies/google-workspace-calendar and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init