browser_error_report
A read tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/browser-error-report.md
What browser_error_report does on Looking Glass
AI agents call browser_error_report 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_error_report is rated Low
The name indicates a reporting/retrieval function consistent with Read operations (gathering diagnostic data). The empty description and naming pattern (similar to sibling tools like 'browser_console_messages', 'browser_analyze_page') suggest it queries browser error state without modification. However, confidence is moderate due to lack of explicit description.
From the tool's definition Tool name 'browser_error_report' suggests retrieving or reporting error information from browser state. Description is empty, limiting specificity.
Attacks that exploit this kind of access
The rule that runs browser_error_report 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_error_report, this is the rule to start with:
browser_error_report 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_error_report call is checked against it from then on.
Questions about browser_error_report
browser_error_report 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_error_report: 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_error_report 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_error_report 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_error_report. 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_error_report 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