List your active browser sessions.
AI agents call browserbeam_list_sessions to retrieve information from Browserbeam MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays information about existing browser sessions without modifying, deleting, or executing any operations. It is a pure read operation on session metadata. The blast radius is minimal—disclosure of session information could enable a follow-up attack but the tool itself performs no action. Severity is low because the impact is limited to information disclosure of already-active sessions.
From the tool's definition Tool name 'list_sessions' and description 'List your active browser sessions' indicate a query/retrieval operation with no side effects. The verb 'list' is characteristic of Read category tools.
Attacks that exploit this kind of access
List your active browser sessions. It is categorised as a Read tool in the Browserbeam MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Browserbeam MCP Server MCP server in PolicyLayer and add a rule for browserbeam_list_sessions: 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 Browserbeam MCP Server. Nothing to install.
browserbeam_list_sessions 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 browserbeam_list_sessions 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 browserbeam_list_sessions. 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.
browserbeam_list_sessions is provided by the Browserbeam MCP Server MCP server (nyku/browserbeam-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 →