browser_diagnose

A other tool on the Looking Glass MCP server.

SERVERLooking Glass SOURCElooking-glass-mcp

Low RISK CLASS

Category Other

Parameters 20 required

Recommended Rate-limitedsee 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-diagnose.md

WHAT IT DOES

What browser_diagnose does on Looking Glass

AI agents call browser_diagnose as a supporting operation in Looking Glass workflows.

Parameter	Type	Required	Description
`error`	string	—	Error message to diagnose (or leave empty for general diagnostics)
`selector`	string	—	CSS selector of the element involved in the error

Parameters from the server's own tool schema.

RISK

Why browser_diagnose is rated Low

The description is empty, so the exact behavior is unknown. Based on the name 'browser_diagnose', it likely reads diagnostic information from the browser (logs, state, errors), suggesting a Read category. However, given the sibling tools context (browser automation with execute/write capabilities), there is uncertainty.

From the tool's definition Tool name is 'browser_diagnose'; description is empty or uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browser_diagnose 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_diagnose, this is the rule to start with:

browser_diagnose Rate-limited

browser_diagnose gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_diagnose": {
      "limits": [
        {
          "counter": "browser_diagnose_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR 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_diagnose call is checked against it from then on.

FAQ

Questions about browser_diagnose

What does the browser_diagnose tool do? +

browser_diagnose is a other tool on the Looking Glass MCP server. It is categorised as a Other tool in the Looking Glass MCP Server, which means it performs auxiliary operations.

What parameters does browser_diagnose accept? +

browser_diagnose accepts 2 parameters: error, selector. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browser_diagnose? +

Register the Looking Glass MCP server in PolicyLayer and add a rule for browser_diagnose: 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_diagnose? +

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

Can I rate-limit browser_diagnose? +

Yes. Add a rate_limit block to the browser_diagnose 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_diagnose completely? +

Set action: deny in the PolicyLayer policy for browser_diagnose. 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_diagnose? +

browser_diagnose 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 →Tool risk categories →MCP tool →