Create or reuse a Browserbase browser session and set it as active.
AI agents invoke browserbase_session_create to trigger actions in Browserbase 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 browser process/resource on Browserbase infrastructure. This is an execution action that spins up a remote browser environment, enabling subsequent web interactions. It's not merely reading data, and while reversible (sessions can be closed), it triggers an external operation whose effects depend on how the session is subsequently used.
From the tool's definition "Create or reuse a Browserbase browser session and set it as active"
Attacks that exploit this kind of access
Create or reuse a Browserbase browser session and set it as active. It is categorised as a Execute tool in the Browserbase MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Browserbase MCP Server MCP server in PolicyLayer and add a rule for browserbase_session_create: 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.
browserbase_session_create 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 browserbase_session_create 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 browserbase_session_create. 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.
browserbase_session_create is provided by the Browserbase MCP Server MCP server (mesuterpikin/mcp-server-browserbase). 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 →