browser_type
Type text into an element with per-keystroke delay (organic). Each character dispatches keydown/keypress/keyup, unlike browser.fill which replaces .value instantly. Use when the page listens to keystroke events or for typing-speed fingerprint checks. ref is an aria-ref token from browser.snapshot...
This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-type.md
What browser_type does on Dialogbrain
AI agents invoke browser_type 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 |
|---|---|---|---|
ref | string | Yes | |
text | string | Yes | |
page_id | string | Yes | |
delay_ms | object | — |
Parameters from the server's own tool schema.
Why browser_type is rated High
This tool performs browser automation by simulating keyboard input into UI elements, dispatching real keystroke events. It executes external browser actions whose effects depend entirely on what element is targeted and what text is typed — it could submit forms, send messages, enter credentials, or trigger any event-driven behavior on a live web page.
From the tool's definition Type text into an element with per-keystroke delay... Each character dispatches keydown/keypress/keyup... Use when the page listens to keystroke events or for typing-speed fingerprint checks
Attacks that exploit this kind of access
The rule that runs browser_type 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_type, this is the rule to start with:
browser_type 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_type call is checked against it from then on.
Questions about browser_type
Type text into an element with per-keystroke delay (organic). Each character dispatches keydown/keypress/keyup, unlike browser.fill which replaces .value instantly. Use when the page listens to keystroke events or for typing-speed fingerprint checks. ref is an aria-ref token from browser.snapshot ('e7') or a CSS selector. delay_ms defaults to 50. 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_type accepts 4 parameters: ref, text, page_id, delay_ms. Required: ref, text, page_id. 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_type: 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_type 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_type 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_type. 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_type 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