Use this when the user asks to screenshot, capture, or take a picture of a webpage/URL, or to render raw HTML or Markdown to an image or PDF. Do NOT use to get a reusable hosted image URL (use rendex_render_link) or to make a branded multi-format document (use render_artifact). Captures a screens...
AI agents call rendex_screenshot 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 |
|---|---|---|---|
js | string | — | Custom JavaScript to execute in the page before capture. Runs in the browser sandbox. Max 50KB. |
css | string | — | Custom CSS to inject into the page before capture. Hide cookie banners, add watermarks, override styles. Max 50KB. |
geo | string | — | ISO 3166-1 alpha-2 country code for geo-targeted capture (e.g., 'US', 'DE', 'JP'). Renders the page as seen from that country. Pro/Enterprise only. Note: CSS/JS |
url | string | — | The webpage URL to capture (a schemeless host like 'example.com' is accepted). Mutually exclusive with 'html' and 'markdown'. |
data | object | — | Key-value data object for Mustache templating. When provided, the 'html' or 'markdown' string is rendered as a logic-less Mustache template before capture — {{v |
html | string | — | Raw HTML to render and capture. Mutually exclusive with 'url' and 'markdown'. Great for invoices, social cards, email templates, OG images. |
delay | integer | — | Milliseconds to wait after page load before capture (useful for JS-rendered content) |
width | integer | — | Viewport width in pixels (320-3840) |
device | string | — | Device preset that sets viewport, scale factor, and user agent in one shot. E.g. 'iphone_15' for a mobile screenshot. Overrides width/height/deviceScaleFactor/u |
format | string | — | Output format — png (lossless), jpeg (smaller), webp (smallest), or pdf (document). Use pdf for invoices, reports, archival. |
height | integer | — | Viewport height in pixels (240-2160) |
cookies | array | — | Cookies to set before capture. Useful for authenticated pages. Max 50 cookies. |
Parameters from the server's own tool schema.
The tool reads/fetches a webpage or renders provided content and returns an image or PDF. It does not modify any data, execute arbitrary code on the user's system, or perform destructive/financial actions. The main risk is that it can fetch arbitrary URLs (potential SSRF or access to internal resources), which raises severity slightly above trivial, but the tool itself is fundamentally a read/capture operation.
From the tool's definition Captures a screenshot or PDF of any webpage, raw HTML, or Markdown. Returns partial renders on timeout by default
Risk signalsAccepts freeform code/query input (js) · Accepts file system path (cookies[].path) · Accepts URL/endpoint input (url) · Accepts raw HTML/template content (html) · High parameter count (49 properties)
Attacks that exploit this kind of access
Use this when the user asks to screenshot, capture, or take a picture of a webpage/URL, or to render raw HTML or Markdown to an image or PDF. Do NOT use to get a reusable hosted image URL (use rendex_render_link) or to make a branded multi-format document (use render_artifact). Captures a screenshot or PDF of any webpage, raw HTML, or Markdown. Supports full-page capture, dark mode, ad blocking, custom viewports, CSS/JS injection, cookie/header injection, PDF output, HTML and Markdown rendering, and progressive fallback for heavy sites. Returns partial renders on timeout by default (bestAttempt mode). Costs 1 render credit per call. Cookie/header injection requires Starter+; geo-targeting requires Pro+. It is categorised as a Read tool in the Rendex Screenshot MCP Server, which means it retrieves data without modifying state.
rendex_screenshot accepts 12 parameters: js, css, geo, url, data, html, delay, width, device, format, height, cookies. 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 rendex_screenshot: 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.
rendex_screenshot 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 rendex_screenshot 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 rendex_screenshot. 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.
rendex_screenshot 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.
rendex_screenshot is one line of Rendex Screenshot's registry record.
The record carries the whole server: 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 →