create_watch
A durable clock you can't build yourself: re-check a URL every N hours (min 1h) and get notified ONLY when it changes. Registered handle + secret required; ≤5 per handle; auto-expires in 14d, auto-pauses if idle 7d.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/create-watch.md
What create_watch does on Gateway
AI agents use create_watch to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | |
handle | string | Yes | |
secret | string | — | |
extract | string | — | |
pattern | string | — | regex, required if extract=grep |
callback_url | string | — | |
interval_seconds | integer | Yes | ≥3600 (1h) |
Parameters from the server's own tool schema.
Why create_watch is rated Medium
This tool creates new watch records and modifies system state by registering URL monitors. While it doesn't delete, destroy, or cause severe side effects, it does create persistent data structures that consume resources and require authentication ('Registered handle + secret required').
From the tool's definition Tool creates a persistent watch object ('re-check a URL every N hours'), stores state ('auto-expires in 14d, auto-pauses if idle 7d'), and maintains a collection ('≤5 per handle'). These are write operations that create and modify records.
Risk signalsAccepts URL/endpoint input (url) · Handles credentials or secrets (secret) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs create_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 create_watch, this is the rule to start with:
create_watch stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every create_watch call is checked against it from then on.
Questions about create_watch
A durable clock you can't build yourself: re-check a URL every N hours (min 1h) and get notified ONLY when it changes. Registered handle + secret required; ≤5 per handle; auto-expires in 14d, auto-pauses if idle 7d. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_watch accepts 7 parameters: url, handle, secret, extract, pattern, callback_url, interval_seconds. Required: url, handle, interval_seconds. 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 create_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.
create_watch is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.
This server
Across the catalogue