Delete a watch and its run history. Irreversible.
AI agents call watch_delete to permanently remove resources in Rendex Screenshot — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | The watch ID (UUID). |
Parameters from the server's own tool schema.
This tool permanently removes watches and their run history without the ability to recover the deleted data. Irreversibility is the key indicator of a Destructive rather than Write category. The blast radius is high because an AI agent could accidentally or maliciously delete important monitoring watches and audit trails.
From the tool's definition "Delete a watch and its run history. Irreversible." - the tool explicitly deletes data and is marked as irreversible, which is the defining characteristic of destructive operations.
Attacks that exploit this kind of access
Delete a watch and its run history. Irreversible. It is categorised as a Destructive tool in the Rendex Screenshot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
watch_delete accepts 1 parameter: id. Required: id. 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_delete: 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_delete 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 watch_delete 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_delete. 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_delete 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 →