Scrape a URL and return its full HTML content. Restrictions: Activated for URLs that require JavaScript rendering or bot protection. Valid: Get HTML from a dynamic, JS-heavy single-page application. Invalid: Fetching a simple static page (use a standard HTTP client).
AI agents call scrape_html to retrieve information from Scrapeless Ai Scrapeless without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves HTML content from web pages. While it accesses external URLs and may trigger server requests, it performs no write, execute, or destructive operations. The description explicitly limits it to returning HTML content, making it a read operation. Severity is low because retrieving public web content poses minimal risk; misuse would result in data retrieval rather than system compromise or data loss.
From the tool's definition Tool name is 'scrape_html' and description states 'Scrape a URL and return its full HTML content' — purely retrieves data with no modification or deletion capability.
Attacks that exploit this kind of access
Scrape a URL and return its full HTML content. Restrictions: Activated for URLs that require JavaScript rendering or bot protection. Valid: Get HTML from a dynamic, JS-heavy single-page application. Invalid: Fetching a simple static page (use a standard HTTP client). It is categorised as a Read tool in the Scrapeless Ai Scrapeless MCP Server, which means it retrieves data without modifying state.
Register the Scrapeless Ai Scrapeless MCP server in PolicyLayer and add a rule for scrape_html: 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 Scrapeless Ai Scrapeless. Nothing to install.
scrape_html 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 scrape_html 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 scrape_html. 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.
scrape_html is provided by the Scrapeless Ai Scrapeless MCP server (@iflow-mcp/scrapeless-ai-scrapeless-mcp-server). 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 →