AI agents call browser_session_status to retrieve information from Wmux without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries the status of an existing browser session. It has no side effects, does not execute code or commands, does not modify data, and does not delete or move resources. The minimal information it could expose (session state, active window/tab details) represents a low risk if accessed by an AI agent misusing it.
From the tool's definition The tool name is 'browser_session_status' with description 'Get current browser session status' — it retrieves the current state of a browser session without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
Get current browser session status. It is categorised as a Read tool in the Wmux MCP Server, which means it retrieves data without modifying state.
Register the Wmux MCP server in PolicyLayer and add a rule for browser_session_status: 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 Wmux. Nothing to install.
browser_session_status 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_session_status 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_session_status. 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_session_status is provided by the Wmux MCP server (openwong2kim/wmux). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
browser_session_status is one line of Wmux's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →