browser_recover

A execute tool on the Looking Glass MCP server.

SERVERLooking Glass SOURCElooking-glass-mcp

High RISK CLASS

Category Execute

Parameters 00 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-recover.md

WHAT IT DOES

What browser_recover does on Looking Glass

AI agents invoke browser_recover to trigger actions in Looking Glass. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why browser_recover is rated High

Based on the tool name and server context (AI-native browser for agents with self-healing capability), 'browser_recover' likely triggers a browser recovery or self-healing action, which falls under Execute. However, the empty description significantly lowers confidence. It could involve restarting browser state or recovering from errors, which is an external operation.

From the tool's definition Tool name 'browser_recover' on a browser automation server; description is empty or uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

browser_recover Rate-limited

browser_recover stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_recover": {
      "limits": [
        {
          "counter": "browser_recover_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT 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_recover call is checked against it from then on.

FAQ

Questions about browser_recover

What does the browser_recover tool do? +

browser_recover is a execute tool on the Looking Glass MCP server. It is categorised as a Execute tool in the Looking Glass MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on browser_recover? +

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

browser_recover is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browser_recover? +

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

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

browser_recover 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 → High-risk tools on this server →

Across the catalogue

browser_click on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →