readability_extract
Extract the main article from a web page (Readability-style content scoring, no headless browser): clean body text with paragraph breaks plus title, byline, site name, published/modified dates, language, excerpt, lead image, word count and reading time. Navigation, ads, share bars, comments and r...
This record as markdown: /tools/com-it-scorptech-x402/readability-extract.md
What readability_extract does on ScorpTech x402 API
AI agents call readability_extract to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | Article URL (http/https, public hosts only) |
maxChars | integer | — | Text cap 500-100000 characters (default 20000) |
paragraphs | boolean | — | Also return the text as a paragraphs array (default false) |
Parameters from the server's own tool schema.
Why readability_extract is rated Low
Even though readability_extract only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs readability_extract safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For readability_extract, this is the rule to start with:
readability_extract is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every readability_extract call is checked against it from then on.
Questions about readability_extract
Extract the main article from a web page (Readability-style content scoring, no headless browser): clean body text with paragraph breaks plus title, byline, site name, published/modified dates, language, excerpt, lead image, word count and reading time. Navigation, ads, share bars, comments and related-links blocks are stripped; JSON-LD articleBody is used when it is fuller. SSRF-safe fetch. Price: $0.01 USDC per successful call (x402, Solana). Same tool over HTTPS: GET https://scorptech.it.com/api/x402/v1/readability-extract. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
readability_extract accepts 3 parameters: url, maxChars, paragraphs. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for readability_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 ScorpTech x402 API. Nothing to install.
readability_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 readability_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 readability_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.
readability_extract is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue