browser_snapshot
Get accessibility snapshot with element refs
This record as markdown: /tools/alexgladkov-claude-in-mobile/browser-snapshot.md
What browser_snapshot does on Claude Mobile
AI agents call browser_snapshot to retrieve information from Claude Mobile 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
This tool reads and returns UI accessibility data (element references and snapshot information) from a mobile device. It has no side effects on the device state, app data, or system configuration. It is purely informational, analogous to a screenshot or introspection query.
From the tool's definition Tool "browser_snapshot" retrieves "accessibility snapshot with element refs" — a query operation that captures UI state without modifying device state or triggering actions.
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 Claude Mobile, 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 Claude Mobile, apply this rule, and every browser_snapshot call is checked against it from then on.
Questions about browser_snapshot
Get accessibility snapshot with element refs. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.
Register the Claude Mobile 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 Claude Mobile. 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 Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Mobile, and thousands of servers like it.
This server
Across the catalogue