Return session id, URL, title, and window information.
AI agents call browser_state to retrieve information from SeleniumMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves current browser state information (session ID, URL, title, window info) without modifying anything. It is a pure read/query operation with minimal blast radius.
From the tool's definition Return session id, URL, title, and window information
Attacks that exploit this kind of access
Return session id, URL, title, and window information. It is categorised as a Read tool in the SeleniumMCP MCP Server, which means it retrieves data without modifying state.
Register the Selenium MCP server in PolicyLayer and add a rule for browser_state: 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 SeleniumMCP. Nothing to install.
browser_state 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_state 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_state. 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_state is provided by the Selenium MCP server (lokii0911/seleniummcp). 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 →