take_snapshot
Take a text snapshot of the currently selected page based on the a11y tree. The snapshot lists page elements along with a unique identifier (uid). Always use the latest snapshot. Prefer taking a snapshot over taking a screenshot. The snapshot indicates the element selected in the DevTools Element...
This record as markdown: /tools/anirbandz-chrome-mcp-devtool/take-snapshot.md
What take_snapshot does on Chrome DevTools MCP
AI agents call take_snapshot to retrieve information from Chrome DevTools MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why take_snapshot is rated Low
This tool retrieves structural information about a webpage's DOM and accessibility tree for inspection and debugging purposes. It is a non-destructive read operation with no side effects. Even though it operates within a browser automation context, the specific action is data retrieval only, making it a Read category tool with low severity.
From the tool's definition Tool description states it 'takes a text snapshot' and 'lists page elements' — operations that retrieve and inspect data from the current page without modifying state. It reads the accessibility tree and reports the currently selected element in DevTools.
Attacks that exploit this kind of access
The rule that runs take_snapshot safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Chrome DevTools MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For take_snapshot, this is the rule to start with:
take_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 Chrome DevTools MCP, apply this rule, and every take_snapshot call is checked against it from then on.
Questions about take_snapshot
Take a text snapshot of the currently selected page based on the a11y tree. The snapshot lists page elements along with a unique identifier (uid). Always use the latest snapshot. Prefer taking a snapshot over taking a screenshot. The snapshot indicates the element selected in the DevTools Elements panel (if any). It is categorised as a Read tool in the Chrome DevTools MCP MCP Server, which means it retrieves data without modifying state.
Register the Chrome DevTools MCP server in PolicyLayer and add a rule for take_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 Chrome DevTools MCP. Nothing to install.
take_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 take_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 take_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.
take_snapshot is provided by the Chrome DevTools MCP server (anirbandz/chrome_mcp_devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Chrome DevTools, and thousands of servers like it.
This server
Across the catalogue