browser_snapshot
A read tool on the Playwright MCP server.
This record as markdown: /tools/hanato238-playwright-mcp/browser-snapshot.md
What browser_snapshot does on Playwright
AI agents call browser_snapshot to retrieve information from Playwright without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why browser_snapshot is rated Low
The tool captures the current state of a web page without modifying or executing actions. While the description is empty, the context from the server description and sibling tools (which include write/execute operations like click, drag, and cookie manipulation) indicates this is a read-only introspection tool.
From the tool's definition Tool name 'browser_snapshot' and server description indicate this retrieves a snapshot of the current browser state for inspection.
Attacks that exploit this kind of access
The rule that runs browser_snapshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Playwright, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_snapshot, this is the rule to start with:
browser_snapshot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Playwright, apply this rule, and every browser_snapshot call is checked against it from then on.
Questions about browser_snapshot
browser_snapshot is a read tool on the Playwright MCP server. It is categorised as a Read tool in the Playwright MCP Server, which means it retrieves data without modifying state.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_snapshot: 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. Nothing to install.
browser_snapshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the browser_snapshot 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.
Set action: deny in the PolicyLayer policy for browser_snapshot. 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.
browser_snapshot is provided by the Playwright MCP server (hanato238/playwright-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Playwright, and thousands of servers like it.
This server
Across the catalogue