Low Risk

browser_screenshot

Capture a screenshot of the current page.

How to control browser_screenshot ↓

What browser_screenshot does on Web Scraper

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

Low Risk

Why browser_screenshot needs a policy

Taking a screenshot is a read-only operation that retrieves visual information about the current state of a web page without modifying, deleting, or executing code. It has no side effects on the target system or data. While it runs within a browser automation context (which could theoretically capture sensitive information), the tool itself performs no write, destructive, or executable actions.

From the tool's definition Tool description states 'Capture a screenshot of the current page' — a passive observation operation with no data modification, deletion, or external execution. The verb 'capture' indicates retrieval only.

Documented attack patterns abuse exactly the kind of access browser_screenshot gives an agent:

How to control browser_screenshot

PolicyLayer is an MCP gateway — it sits between your AI agents and Web Scraper, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_screenshot:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_screenshot": {}
  }
}

browser_screenshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Web Scraper — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browser_screenshot

What does the browser_screenshot tool do? +

Capture a screenshot of the current page. It is categorised as a Read tool in the Web Scraper MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_screenshot? +

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

What risk level is browser_screenshot? +

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

Can I rate-limit browser_screenshot? +

Yes. Add a rate_limit block to the browser_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 browser_screenshot completely? +

Set action: deny in the PolicyLayer policy for browser_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 browser_screenshot? +

browser_screenshot is provided by the Web Scraper MCP server (imyourboyroy/webscrapertoolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Web Scraper tool call.

Start from Web Scraper, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

62 Web Scraper tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.