Use this when the user asks to read, extract, get the text/content/article of, or summarize a webpage/URL. Do NOT use for a visual screenshot (use rendex_screenshot). Extracts clean reader-mode content from any webpage as Markdown, JSON, or HTML. Runs the same Chromium render pass as a screenshot...
AI agents call rendex_extract 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 |
|---|---|---|---|
url | string | Yes | The webpage URL to extract readable content from (a schemeless host like 'example.com' is accepted). |
device | string | — | Device preset that sets viewport, scale factor, and user agent in one shot. E.g. 'iphone_15' to extract the mobile version of a page. |
timeout | integer | — | Maximum seconds to wait for page load (5-60). Cloudflare has a 60s hard cap. |
blockAds | boolean | — | Block ads and trackers before extraction |
waitUntil | string | — | Page readiness event. networkidle2 (default) is best for most sites. Use domcontentloaded for speed, networkidle0 for completeness. |
extractFormat | string | — | Output shape — markdown (default, LLM-friendly prose), json (structured fields: title/byline/excerpt/siteName/length), or html (cleaned reader-mode HTML). |
hideSelectors | array | — | CSS selectors to hide (display:none) before extraction. E.g. ['.modal', '#newsletter-popup'] to remove overlays. Max 50 selectors. |
blockCookieBanners | boolean | — | Hide common cookie/consent walls (GDPR/CCPA banners) before extraction. A curated selector list, lighter than custom hideSelectors. |
Parameters from the server's own tool schema.
rendex_extract retrieves and queries webpage content without altering or deleting anything. It performs data extraction and transformation for reading purposes only. The tool explicitly contrasts itself with rendex_screenshot (visual capture) and focuses on content retrieval. There are no write, execute, destructive, or financial operations involved.
From the tool's definition Tool description states: "Use this when the user asks to read, extract, get the text/content/article of, or summarize a webpage/URL." It "Extracts clean reader-mode content from any webpage as Markdown, JSON, or HTML" and returns "the article body plus title,…
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
Use this when the user asks to read, extract, get the text/content/article of, or summarize a webpage/URL. Do NOT use for a visual screenshot (use rendex_screenshot). Extracts clean reader-mode content from any webpage as Markdown, JSON, or HTML. Runs the same Chromium render pass as a screenshot, so it captures content after JavaScript runs — handles SPAs that fetch-only readers miss. Strips nav, ads, and boilerplate, returning the article body plus title, byline, and excerpt. Great for feeding page content to an LLM, summarization, or RAG ingestion. Costs 1 render credit per call. It is categorised as a Read tool in the Rendex Screenshot MCP Server, which means it retrieves data without modifying state.
rendex_extract accepts 8 parameters: url, device, timeout, blockAds, waitUntil, extractFormat, hideSelectors, blockCookieBanners. Required: url. 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_extract: 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_extract 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_extract 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_extract. 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_extract 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 →