watch_get

Fetch one watch by ID, including its current baseline image URL and status. Returns JSON.

Server Rendex Screenshot copperline-labs/rendex-mcp
Category Read
Risk class Low
Parameters 11 required

What watch_get does on Rendex Screenshot

AI agents call watch_get 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.

ParameterTypeRequiredDescription
id string Yes The watch ID (UUID).

Parameters from the server's own tool schema.

Why watch_get needs a policy

This tool retrieves metadata about a watch (baseline image URL and status) by ID. It performs a simple lookup operation with no data modification, deletion, or execution of external operations. The returned data is read-only baseline information used for comparison purposes. No reversible or irreversible modifications, code execution, or financial transactions are involved.

From the tool's definition Tool name 'watch_get' and description 'Fetch one watch by ID' indicates data retrieval. The phrase 'Returns JSON' confirms it retrieves and queries data without side effects.

Questions about watch_get

What does the watch_get tool do? +

Fetch one watch by ID, including its current baseline image URL and status. Returns JSON. It is categorised as a Read tool in the Rendex Screenshot MCP Server, which means it retrieves data without modifying state.

What parameters does watch_get accept? +

watch_get accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on watch_get? +

Register the Rendex Screenshot MCP server in PolicyLayer and add a rule for watch_get: 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.

What risk level is watch_get? +

watch_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit watch_get? +

Yes. Add a rate_limit block to the watch_get 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.

How do I block watch_get completely? +

Set action: deny in the PolicyLayer policy for watch_get. 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.

What MCP server provides watch_get? +

watch_get 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.