scrape_screenshot

Capture a high-quality screenshot of any webpage. Restrictions: Bypasses bot detection and CAPTCHAs using residential proxies. Valid: Get a screenshot of a price-checker page protected by Cloudflare. Invalid: Taking a screenshot of the local browser (use browser_screenshot)

Server Scrapeless scrapeless-mcp-server
Category Read
Risk class Low
Parameters 00 required

What scrape_screenshot does on Scrapeless

AI agents call scrape_screenshot to retrieve information from Scrapeless without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why scrape_screenshot needs a policy

This tool reads/retrieves visual content from a webpage by taking a screenshot. It has no write, execute, or destructive side effects on data. The use of residential proxies and bot/CAPTCHA bypass slightly elevates concern but the action itself is purely read-oriented. Severity is low as the worst-case misuse is capturing content from protected pages without authorization.

From the tool's definition Capture a high-quality screenshot of any webpage

Questions about scrape_screenshot

What does the scrape_screenshot tool do? +

Capture a high-quality screenshot of any webpage. Restrictions: Bypasses bot detection and CAPTCHAs using residential proxies. Valid: Get a screenshot of a price-checker page protected by Cloudflare. Invalid: Taking a screenshot of the local browser (use browser_screenshot). It is categorised as a Read tool in the Scrapeless MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on scrape_screenshot? +

Register the Scrapeless MCP server in PolicyLayer and add a rule for scrape_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 Scrapeless. Nothing to install.

What risk level is scrape_screenshot? +

scrape_screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit scrape_screenshot? +

Yes. Add a rate_limit block to the scrape_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.

How do I block scrape_screenshot completely? +

Set action: deny in the PolicyLayer policy for scrape_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.

What MCP server provides scrape_screenshot? +

scrape_screenshot is provided by the Scrapeless MCP server (scrapeless-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.