browser_snapshot_state

A read tool on the Looking Glass MCP server.

SERVERLooking Glass SOURCElooking-glass-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-snapshot-state.md

WHAT IT DOES

What browser_snapshot_state does on Looking Glass

AI agents call browser_snapshot_state to retrieve information from Looking Glass without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why browser_snapshot_state is rated Low

Despite the empty description, the tool name and peer tools strongly suggest this captures or retrieves the current state of the browser (DOM, state variables, etc.) without modifying it. This is consistent with 'snapshot' operations which are inherently read-only.

From the tool's definition Tool name 'browser_snapshot_state' with no description provided; inferred from context of sibling browser tools (browser_analyze_page, browser_console_messages, browser_diagnose) which are read-only inspection tools.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_snapshot_state safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_snapshot_state, this is the rule to start with:

browser_snapshot_state Allowed

browser_snapshot_state is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_snapshot_state": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every browser_snapshot_state call is checked against it from then on.

FAQ

Questions about browser_snapshot_state

What does the browser_snapshot_state tool do? +

browser_snapshot_state is a read tool on the Looking Glass MCP server. It is categorised as a Read tool in the Looking Glass MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_snapshot_state? +

Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_snapshot_state: 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 Looking Glass. Nothing to install.

What risk level is browser_snapshot_state? +

browser_snapshot_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit browser_snapshot_state? +

Yes. Add a rate_limit block to the browser_snapshot_state 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.

How do I block browser_snapshot_state completely? +

Set action: deny in the PolicyLayer policy for browser_snapshot_state. 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.

What MCP server provides browser_snapshot_state? +

browser_snapshot_state is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Looking Glass, and thousands of servers like it.

This server

All 71 Looking Glass tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →