browser_screenshot

Capture screenshot of the page Use when native WebFetch is wrong because you need real browser automation — JS-heavy SPA scraping, login flows with cookie reuse, replay against DOM-drifted versions, AIDefence PII gating before content reaches Claude. For static HTML pages, native WebFetch is fast...

SERVERClaude Flow SOURCEclaude-flow

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ruvnet-claude-flow/browser-screenshot.md

WHAT IT DOES

What browser_screenshot does on Claude Flow

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

RISK

Why browser_screenshot is rated Low

The tool captures (reads) a visual snapshot of a browser page. It does not write, delete, or execute arbitrary code directly. However, it involves real browser automation including login flows with cookie reuse, which means it can access authenticated sessions and capture potentially sensitive content (PII gating is mentioned).

From the tool's definition Capture screenshot of the page — JS-heavy SPA scraping, login flows with cookie reuse, replay against DOM-drifted versions

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_screenshot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_screenshot, this is the rule to start with:

browser_screenshot Allowed

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_screenshot": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every browser_screenshot call is checked against it from then on.

FAQ

Questions about browser_screenshot

What does the browser_screenshot tool do? +

How do I enforce a policy on browser_screenshot? +

Register the Claude Flow 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 Claude Flow. 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 Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

browser_screenshot on Percepta MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →