List your watches (newest first), optionally filtered by status and paged. Returns { items, nextCursor }.
AI agents call watch_list to retrieve information from Rendex Screenshot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Page size (1–100). |
cursor | string | — | Pagination cursor from a previous nextCursor. |
status | string | — | Filter by status. |
Parameters from the server's own tool schema.
This tool queries and retrieves existing watch configurations without creating, modifying, deleting, or executing operations. The 'list' operation with optional filtering and pagination is a standard read-only data retrieval pattern with no side effects. Severity is low because exposure would only leak information about user watches, not compromise system integrity or enable harmful actions.
From the tool's definition Tool name 'watch_list' and description 'List your watches' indicates a retrieval operation. Returns paginated results without modifying data.
Attacks that exploit this kind of access
List your watches (newest first), optionally filtered by status and paged. Returns { items, nextCursor }. It is categorised as a Read tool in the Rendex Screenshot MCP Server, which means it retrieves data without modifying state.
watch_list accepts 3 parameters: limit, cursor, status. 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_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the watch_list 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_list. 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_list 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 →