cancel_watch
Cancel one of your watches (watch_id from list_watches). Requires handle + secret.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/cancel-watch.md
What cancel_watch does on Gateway
AI agents call cancel_watch to permanently remove resources in Gateway, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
handle | string | Yes | |
secret | string | — | |
watch_id | string | Yes |
Parameters from the server's own tool schema.
Why cancel_watch is rated Critical
Cancelling a watch removes it permanently; there is no indication of an undo or restore operation. This maps to Destructive. Severity is medium because the blast radius is limited to the loss of a single watch/notification subscription, not broader data or financial impact.
From the tool's definition Cancel one of your watches — cancellation is an irreversible deletion of the watch resource
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs cancel_watch safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancel_watch, this is the rule to start with:
cancel_watch is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every cancel_watch call is checked against it from then on.
Questions about cancel_watch
Cancel one of your watches (watch_id from list_watches). Requires handle + secret. It is categorised as a Destructive tool in the Gateway MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
cancel_watch accepts 3 parameters: handle, secret, watch_id. Required: handle, watch_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for cancel_watch: 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 Gateway. Nothing to install.
cancel_watch is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel_watch 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 cancel_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.
cancel_watch is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
Across the catalogue