browser_open
Open a URL in a remote browser. Saved login cookies are auto-attached when the URL domain matches a claimed browser identity. Pass identity_name to override auto-matching or force a specific identity.
This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-open.md
What browser_open does on Dialogbrain
AI agents invoke browser_open to trigger actions in Dialogbrain. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
url | string | Yes | |
identity_name | object | — |
Parameters from the server's own tool schema.
Why browser_open is rated High
This tool executes browser actions against remote URLs using saved login sessions. An AI agent could navigate to arbitrary URLs with authenticated credentials, enabling account actions, data exfiltration, or unintended operations on behalf of logged-in identities. This is an Execute-category tool with high severity due to the auto-attached authentication cookies amplifying blast radius.
From the tool's definition 'Open a URL in a remote browser' — triggers external browser operations; 'Saved login cookies are auto-attached' — executes authenticated browser sessions with stored credentials
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs browser_open safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dialogbrain, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browser_open, this is the rule to start with:
browser_open stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Dialogbrain, apply this rule, and every browser_open call is checked against it from then on.
Questions about browser_open
Open a URL in a remote browser. Saved login cookies are auto-attached when the URL domain matches a claimed browser identity. Pass identity_name to override auto-matching or force a specific identity. It is categorised as a Execute tool in the Dialogbrain MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_open accepts 2 parameters: url, identity_name. Required: url. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain MCP server in PolicyLayer and add a rule for browser_open: 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 Dialogbrain. Nothing to install.
browser_open 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 browser_open 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 browser_open. 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.
browser_open is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
Across the catalogue