// SCAN REPORT

Rendex Screenshot

13 tools. 5 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 29 Jun 2026

5 can modify or destroy data

8 read-only

13 tools total

Verified server · catalogue entry verified 29/06/2026 · full schemas captured for 12 of 13 tools

How to control Rendex Screenshot ↓

TOOL MAP

What Rendex Screenshot exposes to your agents

Read (8) Write / Execute (4) Destructive / Financial (1)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Rendex Screenshot costs in tokens

9,923 tokens of tool definitions, loaded on every request

5.0% of a 200k context window

2,043 heaviest tool: rendex_render_link

Full per-tool breakdown → Model it in the token calculator →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Rendex Screenshot tools

Destructive · High watch_delete This tool permanently removes watches and their run history without the ability to recover the deleted data. Execute · Medium rendex_render_link This tool triggers an external operation (rendering and hosting an image) on a remote service, producing a persistent hosted artifact. Execute · Medium render_artifact This tool triggers an external rendering operation that produces and hosts files (PDF, PNG, share page), consuming render credits in the process. Write · Medium watch_create This tool creates a persistent monitoring resource (a 'watch') that schedules recurring captures and notifications.

5 of Rendex Screenshot's 13 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Rendex Screenshot

PolicyLayer is an MCP gateway — it sits between your AI agents and Rendex Screenshot, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "watch_delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "watch_create": {
    "limits": [
      {
        "counter": "watch_create_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "rendex_account": {
    "limits": [
      {
        "counter": "rendex_account_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Rendex Screenshot — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON RENDEX SCREENSHOT →

Instant setup, no code required.

FULL CATALOGUE

All 13 Rendex Screenshot tools

DESTRUCTIVE 1 tools

Destructive watch_delete Delete a watch and its run history. Irreversible.

EXECUTE 2 tools

Execute render_artifact Use this when the user asks to make or create a branded report, invoice, summary, release notes, or document — Execute rendex_render_link Use this when the user wants a reusable, HOSTED image URL — an og:image or a link to embed in an <img> tag — r

WRITE 2 tools

Write watch_create Use this when the user asks to monitor, watch, or track a webpage for changes, or to be alerted/notified when Write watch_update Update a watch in place — pause/resume (paused), re-point (url), change schedule/diff/notify settings, or turn

READ 8 tools

Read rendex_account Check the Rendex account: which plan it's on, how many render credits have been used vs. the monthly limit (an Read rendex_extract Use this when the user asks to read, extract, get the text/content/article of, or summarize a webpage/URL. Do Read rendex_screenshot Use this when the user asks to screenshot, capture, or take a picture of a webpage/URL, or to render raw HTML Read watch_get Fetch one watch by ID, including its current baseline image URL and status. Returns JSON. Read watch_list List your watches (newest first), optionally filtered by status and paged. Returns { items, nextCursor }. Read watch_run Run an immediate check now (charges 1 credit). Returns the queued run; poll watch_runs for the result or recei Read watch_runs Read a watch's run history (newest first), paged. Each run includes changed, diffScore, and signed before/afte Read watch_test Dry-run a watch config BEFORE creating it — render the proposed config once and report what was captured + whe

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Rendex Screenshot

Can an AI agent delete data through the Rendex Screenshot MCP server? +

Yes. The Rendex Screenshot server exposes 1 destructive tools including watch_delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Rendex Screenshot? +

The Rendex Screenshot server has 2 write tools including watch_create, watch_update. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Rendex Screenshot.

How many tools does the Rendex Screenshot MCP server expose? +

13 tools across 3 categories: Destructive, Read, Write. 8 are read-only. 5 can modify, create, or delete data.

How do I enforce a policy on Rendex Screenshot? +

Register the Rendex Screenshot MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Rendex Screenshot tool call.

Deterministic rules across all 13 Rendex Screenshot tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON RENDEX SCREENSHOT →

Instant setup, no code required.

13 Rendex Screenshot tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Rendex Screenshot's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →