Check if the browser is running and accessible on port 9222 (see browser_docs)
AI agents call browser_health_check to retrieve information from Browser MCP Server 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 read-only operation that verifies the browser service availability by checking connectivity to port 9222. It retrieves status information without modifying, executing, or deleting anything. The low severity reflects minimal blast radius: misuse simply reports incorrect status and does not affect system state.
From the tool's definition Tool name 'browser_health_check' and description 'Check if the browser is running and accessible' indicate a status query operation with no side effects.
Attacks that exploit this kind of access
Check if the browser is running and accessible on port 9222 (see browser_docs). It is categorised as a Read tool in the Browser MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browser MCP Server MCP server in PolicyLayer and add a rule for browser_health_check: 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 Browser MCP Server. Nothing to install.
browser_health_check 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_health_check 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_health_check. 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_health_check is provided by the Browser MCP Server MCP server (madebytokens/browser-mcp-server). 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 →