Diagnose Chrome remote-debugging connectivity and return concrete repair commands.
AI agents call repair_browser_connection to retrieve information from JS Reverse MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool primarily reads/queries the state of the Chrome remote-debugging connection and returns diagnostic information plus repair commands. It does not appear to execute those commands itself — it 'returns' them, making it essentially a read/diagnostic operation. However, some ambiguity exists around 'concrete repair commands' potentially implying side effects.
From the tool's definition Diagnose Chrome remote-debugging connectivity and return concrete repair commands
Attacks that exploit this kind of access
Diagnose Chrome remote-debugging connectivity and return concrete repair commands. It is categorised as a Read tool in the JS Reverse MCP MCP Server, which means it retrieves data without modifying state.
Register the JS Reverse MCP server in PolicyLayer and add a rule for repair_browser_connection: 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 JS Reverse MCP. Nothing to install.
repair_browser_connection 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 repair_browser_connection 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 repair_browser_connection. 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.
repair_browser_connection is provided by the JS Reverse MCP server (noone-hub/jsreverser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →