Low Risk

browser_screenshot

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: Wheth...

Part of the Playwright Stealth server.

browser_screenshot is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE PLAYWRIGHT STEALTH →

Free to start. No card required.

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.

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.

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

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

See the full Playwright Stealth policy for all 6 tools.

Get this rule live on your own Playwright Stealth server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY PLAYWRIGHT STEALTH →

These attack patterns abuse exactly the kind of access browser_screenshot gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so browser_screenshot only ever does what you allow.

SECURE PLAYWRIGHT STEALTH →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

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? +

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

Enforce policy on every Playwright Stealth tool call.

Deterministic rules across all 6 Playwright Stealth tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.