Capture accessibility snapshot of the current page, this is better than screenshot
AI agents call browser_snapshot to retrieve information from Limetest MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves page state information without side effects. It is a read-only operation that captures accessibility metadata from the DOM. Snapshot/screenshot tools are canonical examples of Read operations. While it is part of a testing suite with Execute-category tools (browser_click, browser_drag, etc.), this specific tool performs only data retrieval.
From the tool's definition Tool captures a snapshot (accessibility snapshot) of the current page. Does not modify, execute external operations, delete data, or move money. Described as 'better than screenshot' - a passive observation capability.
Attacks that exploit this kind of access
Capture accessibility snapshot of the current page, this is better than screenshot. It is categorised as a Read tool in the Limetest MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Limetest MCP Server 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 Limetest MCP Server. 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 Limetest MCP Server MCP server (m2rads/limetest-arch). 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 →