browser_attach_identity
Switch the page's identity by loading saved cookies + storage. Use only when switching identity mid-page; for first navigation, pass identity_name to browser.open instead.
This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-attach-identity.md
What browser_attach_identity does on Dialogbrain
AI agents use browser_attach_identity to create or update resources in Dialogbrain, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dialogbrain environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
page_id | string | Yes | |
identity_name | string | Yes |
Parameters from the server's own tool schema.
Why browser_attach_identity is rated Medium
This tool modifies browser state by changing the active identity through cookies and storage, enabling switching between accounts or contexts. While not creating persistent data structures, it materially alters session state in a reversible manner (can switch back).
From the tool's definition Tool description states it loads and applies saved cookies + storage to a page, which modifies the browser's session state and user identity context.
Attacks that exploit this kind of access
The rule that runs browser_attach_identity 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_attach_identity, this is the rule to start with:
browser_attach_identity stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_attach_identity call is checked against it from then on.
Questions about browser_attach_identity
Switch the page's identity by loading saved cookies + storage. Use only when switching identity mid-page; for first navigation, pass identity_name to browser.open instead. It is categorised as a Write tool in the Dialogbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
browser_attach_identity accepts 2 parameters: page_id, identity_name. Required: page_id, identity_name. 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_attach_identity: 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_attach_identity is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the browser_attach_identity 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_attach_identity. 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_attach_identity 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.
This server
Across the catalogue