Check browser connectivity and active page readiness before running reverse workflows.
AI agents call check_browser_health 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.
This tool performs a health check—a non-destructive status query of the browser environment. It retrieves state information (connectivity, page readiness) but does not execute scripts, modify data, delete resources, or trigger side effects. It is purely informational, suitable for validation before running other workflows. The low severity reflects minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'check_browser_health' and description 'Check browser connectivity and active page readiness' indicate a diagnostic query operation with no data modification or code execution.
Attacks that exploit this kind of access
Check browser connectivity and active page readiness before running reverse workflows. 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 check_browser_health: 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.
check_browser_health 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 check_browser_health 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 check_browser_health. 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.
check_browser_health 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 →