Get the current status and metadata of a session.
AI agents call browserbeam_get_session 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 session status and metadata without modifying, executing, or deleting any data. It is purely informational, making it a Read category tool with low severity since an AI agent cannot cause harm by querying session metadata.
From the tool's definition Tool name 'browserbeam_get_session' and description 'Get the current status and metadata of a session' indicate a retrieval operation with no side effects. The word 'Get' explicitly signals a read operation.
Attacks that exploit this kind of access
Get the current status and metadata of a session. 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_get_session: 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_get_session 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_get_session 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_get_session. 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_get_session 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 →