Stop watching a resource channel
Risk signalsTerminates push notification subscriptions
Part of the Google Workspace Calendar (gws CLI) server.
Free to start. No card required.
AI agents invoke calendar_channels_stop to trigger processes or run actions in Google Workspace Calendar (gws CLI). Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
calendar_channels_stop can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"calendar_channels_stop": {
"limits": [
{
"counter": "calendar_channels_stop_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Google Workspace Calendar (gws CLI) policy for all 37 tools.
These attack patterns abuse exactly the kind of access calendar_channels_stop gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Stop watching a resource channel. It is categorised as a Execute tool in the Google Workspace Calendar (gws CLI) MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Google Workspace Calendar (gws CLI) MCP server in PolicyLayer and add a rule for calendar_channels_stop: 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 Workspace Calendar (gws CLI). Nothing to install.
calendar_channels_stop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the calendar_channels_stop 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 calendar_channels_stop. 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.
calendar_channels_stop is provided by the Google Workspace Calendar (gws CLI) MCP server (@gws mcp -s calendar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 37 Google Workspace Calendar (gws CLI) tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.