Take a text snapshot of the currently selected page. The snapshot lists page elements along with a unique identifier (uid). Always use the latest snapshot. Prefer taking a snapshot over taking a screenshot.
AI agents call take_snapshot to retrieve information from Chrome DevTools MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool captures and retrieves information about the current page structure and elements but does not execute code, modify data, delete anything, or trigger external side effects. It is purely observational, similar to inspection or query operations.
From the tool's definition Tool description states it 'Take[s] a text snapshot of the currently selected page' and 'lists page elements along with a unique identifier (uid)'. These are read-only operations that retrieve and inspect page state without modification.
Attacks that exploit this kind of access
Take a text snapshot of the currently selected page. The snapshot lists page elements along with a unique identifier (uid). Always use the latest snapshot. Prefer taking a snapshot over taking a screenshot. 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 (shay5555-gif/chrome-devtools-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →