Create a new browser session. Optionally navigate to a URL. The response already includes page markdown and interactive element refs -- use this as your first observation instead of calling observe separately. Page markdown defaults to a 12,000-character cap; if truncated, call browserbeam_observ...
AI agents invoke browserbeam_create_session to trigger actions in Browserbeam MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Creating a browser session initiates an external process (a real browser instance) and optionally navigates to a URL, triggering external operations. This is an Execute-level action as it spins up browser infrastructure and performs web interactions, though it is reversible via browserbeam_close.
From the tool's definition Create a new browser session. Optionally navigate to a URL.
Attacks that exploit this kind of access
Create a new browser session. Optionally navigate to a URL. The response already includes page markdown and interactive element refs -- use this as your first observation instead of calling observe separately. Page markdown defaults to a 12,000-character cap; if truncated, call browserbeam_observe with a higher max_text_length or browserbeam_scroll_collect for long pages. When finished with the session, you MUST call browserbeam_close. It is categorised as a Execute tool in the Browserbeam MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Browserbeam MCP Server MCP server in PolicyLayer and add a rule for browserbeam_create_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_create_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the browserbeam_create_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_create_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_create_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 →