browser_screenshot

// WHEN AI AGENTS USE THIS TOOL

AI agents call browser_screenshot to retrieve information from Playwright Stealth without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

// WHY ENFORCE A POLICY ON BROWSER_SCREENSHOT

Even though browser_screenshot only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

playwright-stealth.yaml

tools:
  browser_screenshot:
    rules:
      - action: allow

See the full Playwright Stealth policy for all 6 tools.

// DETAILS

Tool Name browser_screenshot

Category Read

MCP Server Playwright Stealth MCP Server

Risk Level Low

// MORE PLAYWRIGHT STEALTH TOOLS

Execute browser_execute Execute browser_start_recording Execute browser_stop_recording Write browser_close Read browser_get_state

// WHAT CAN GO WRONG

Agents calling read-class tools like browser_screenshot have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Open Library MCP Server get_author_info Open Library MCP Server get_author_photo Open Library MCP Server get_authors_by_name Open Library MCP Server get_book_by_id Open Library MCP Server get_book_by_title Open Library MCP Server get_book_cover

// RELATED READING

// FAQ

What does the browser_screenshot tool do? +

Take a screenshot of the current page, a specific element, or a page region. Captures the visible viewport, full page, a specific element, or a rectangular region as a PNG image. Screenshots are saved to filesystem storage and can be accessed later via MCP resources. **Parameters:** - `fullPage`: Whether to capture the full scrollable page (default: false) - `selector`: CSS selector of a specific element to screenshot (e.g., '#main-content', '.hero-banner', 'table.results') - `clip`: Region of the page to screenshot as {x, y, width, height} in pixels - `resultHandling`: How to handle the result: - `saveAndReturn` (default): Saves to storage AND returns inline base64 image - `saveOnly`: Saves to storage and returns only the resource URI (more efficient for large screenshots) **Note:** `fullPage`, `selector`, and `clip` are mutually exclusive. Only one can be specified per call. **Returns:** - With `saveAndReturn`: Inline base64 PNG image data plus a resource_link to the saved file - With `saveOnly`: A resource_link with the `file://` URI to the saved screenshot **Dimension Limits:** Full-page screenshots are limited to 8000 pixels in any dimension. If a full-page screenshot would exceed this limit, it is automatically clipped from the top-left corner and a warning is included in the response. Element and clip screenshots are not subject to this limit. **Use cases:** - Verify page state after navigation - Screenshot a specific element like a chart, table, or form - Capture a region of the page by coordinates - Debug automation issues - Store screenshots for later reference via MCP resources. It is categorised as a Read tool in the Playwright Stealth MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_screenshot? +

Add a rule in your Intercept YAML policy under the tools section for browser_screenshot. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Playwright Stealth MCP server.

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 Intercept 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 Intercept 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 Playwright Stealth MCP server (playwright-stealth-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Playwright Stealth