Use this when the user asks to monitor, watch, or track a webpage for changes, or to be alerted/notified when a page changes. Do NOT use for a one-time capture (use rendex_screenshot). Creates a Rendex Watch — monitors a URL on a schedule and notifies when it changes (real-Chrome visual diff with...
AI agents use watch_create to create or update resources in Rendex Screenshot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rendex Screenshot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | The page to monitor (a schemeless host like 'rendex.dev/pricing' is upgraded to https). |
name | string | — | Optional label for the watch. |
paused | boolean | — | Create the watch paused (no baseline capture or charge until resumed). |
diffMode | string | — | visual = pixel diff + highlighted overlay; text = extracted-text diff; both runs each. |
aiSummary | boolean | — | Pro+ — attach an AI 'what changed' summary (roadmap). |
threshold | number | — | Visual-change noise floor as a 0..1 fraction; the diff must EXCEED it to count as changed. |
webhookUrl | string | — | Starter+ — HMAC-signed change-webhook target. |
notifyEmail | string | — | Any plan — send change alerts here. Must be your OWN account email (others are rejected). Defaults to it if omitted. |
renderParams | object | — | Render knobs applied on every check (a subset of the screenshot capture params). |
intervalMinutes | integer | — | Check frequency in minutes. Minimum is your plan's floor — Free 1440 (daily), Starter 180, Pro 30, Enterprise 5. |
Parameters from the server's own tool schema.
This tool creates a persistent monitoring resource (a 'watch') that schedules recurring captures and notifications. It is a reversible write operation (watches can be deleted via watch_delete). It does not execute arbitrary code or delete data, making Write the appropriate category.
From the tool's definition Creates a Rendex Watch — monitors a URL on a schedule and notifies when it changes... Returns the created watch as JSON.
Risk signalsAccepts URL/endpoint input (url) · High parameter count (36 properties)
Attacks that exploit this kind of access
Use this when the user asks to monitor, watch, or track a webpage for changes, or to be alerted/notified when a page changes. Do NOT use for a one-time capture (use rendex_screenshot). Creates a Rendex Watch — monitors a URL on a schedule and notifies when it changes (real-Chrome visual diff with a highlighted overlay, an extracted-text diff, or both). An active watch captures its baseline immediately. Returns the created watch as JSON. It is categorised as a Write tool in the Rendex Screenshot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
watch_create accepts 10 parameters: url, name, paused, diffMode, aiSummary, threshold, webhookUrl, notifyEmail, renderParams, intervalMinutes. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Rendex Screenshot MCP server in PolicyLayer and add a rule for watch_create: 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 Rendex Screenshot. Nothing to install.
watch_create 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 watch_create 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 watch_create. 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.
watch_create is provided by the Rendex Screenshot MCP server (copperline-labs/rendex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →