browser_diff_state
A read tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-diff-state.md
What browser_diff_state does on Looking Glass
AI agents call browser_diff_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.
Why browser_diff_state is rated Low
The name implies a diffing/comparison operation (Read), but the empty description significantly lowers confidence. Diff operations typically read and compare state without side effects. Given the browser automation context, misuse risk is medium as state inspection could expose sensitive data.
From the tool's definition Tool name 'browser_diff_state' suggests comparing or reading browser state differences; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs browser_diff_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_diff_state, this is the rule to start with:
browser_diff_state 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 Looking Glass, apply this rule, and every browser_diff_state call is checked against it from then on.
Questions about browser_diff_state
browser_diff_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.
Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_diff_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.
browser_diff_state 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_diff_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.
Set action: deny in the PolicyLayer policy for browser_diff_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.
browser_diff_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.
More on Looking Glass, and thousands of servers like it.
This server
Across the catalogue