Capture accessibility snapshot of the current page. Use this for getting references to elements to interact with.
AI agents call browser_snapshot to retrieve information from YetiBrowser MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries page data (accessibility tree/DOM snapshot) with no side effects. This is a read-only information gathering operation that enables subsequent interactions but does not itself modify state, execute commands, or cause destructive changes. Belongs in Read category.
From the tool's definition Tool captures accessibility snapshot of the current page for getting references to elements. No modification, deletion, or code execution occurs—purely retrieves state information about the DOM and page structure.
Documented attack patterns abuse exactly the kind of access browser_snapshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and YetiBrowser MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_snapshot:
{
"version": "1",
"default": "deny",
"tools": {
"browser_snapshot": {}
}
} browser_snapshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Capture accessibility snapshot of the current page. Use this for getting references to elements to interact with. It is categorised as a Read tool in the YetiBrowser MCP MCP Server, which means it retrieves data without modifying state.
Register the YetiBrowser 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 YetiBrowser MCP. 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 YetiBrowser MCP server (yetidevworks/yetibrowser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from YetiBrowser MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 YetiBrowser MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.