ONLY WORKS WITH MULTI-SESSION TOOLS! Track all parallel sessions: Critical tool for multi-session management! Shows all active browser sessions with their IDs, names, ages, and Browserbase session IDs. Use this frequently to monitor your parallel automation workflows, verify sessions are running,...
AI agents call multi_browserbase_stagehand_session_list to retrieve information from Browserbase MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure query/retrieval tool that returns session information for monitoring purposes. It has no side effects—it does not create, modify, delete, or execute actions. The only impact is informational, used for tracking and debugging existing sessions. Severity is low because disclosure of session metadata poses minimal security risk if proper access controls are in place.
From the tool's definition Tool lists and displays all active browser sessions with their metadata (IDs, names, ages, Browserbase session IDs).
Attacks that exploit this kind of access
ONLY WORKS WITH MULTI-SESSION TOOLS! Track all parallel sessions: Critical tool for multi-session management! Shows all active browser sessions with their IDs, names, ages, and Browserbase session IDs. Use this frequently to monitor your parallel automation workflows, verify sessions are running, and get session IDs for session-specific tools. Essential for debugging and resource management in complex multi-browser scenarios. It is categorised as a Read tool in the Browserbase MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browserbase MCP Server MCP server in PolicyLayer and add a rule for multi_browserbase_stagehand_session_list: 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 Browserbase MCP Server. Nothing to install.
multi_browserbase_stagehand_session_list 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 multi_browserbase_stagehand_session_list 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 multi_browserbase_stagehand_session_list. 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.
multi_browserbase_stagehand_session_list is provided by the Browserbase MCP Server MCP server (ronsdad/mcp-server-browserbase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
multi_browserbase_stagehand_session_list is one line of Browserbase MCP Server'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 →