browser_fill_form
Fill multiple form fields in one call. fields is a list of {ref, value} dicts. ref is a CSS selector; value is a string (text) or boolean (checkbox). Saves N round-trips vs calling browser.fill repeatedly.
This record as markdown: /tools/io-github-saloprj-dialogbrain/browser-fill-form.md
What browser_fill_form does on Dialogbrain
AI agents invoke browser_fill_form 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 |
|---|---|---|---|
fields | array | Yes | |
page_id | string | Yes |
Parameters from the server's own tool schema.
Why browser_fill_form is rated High
This tool executes browser actions by filling form fields using CSS selectors and values. It directly manipulates web page state, which could trigger submissions, modify account data, or perform actions depending on what forms are targeted. The ability to fill arbitrary forms in a browser context represents significant risk if misused by an AI agent.
From the tool's definition Fill multiple form fields in one call... ref is a CSS selector; value is a string (text) or boolean (checkbox)
Attacks that exploit this kind of access
The rule that runs browser_fill_form 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_fill_form, this is the rule to start with:
browser_fill_form 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_fill_form call is checked against it from then on.
Questions about browser_fill_form
Fill multiple form fields in one call. fields is a list of {ref, value} dicts. ref is a CSS selector; value is a string (text) or boolean (checkbox). Saves N round-trips vs calling browser.fill repeatedly. 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_fill_form accepts 2 parameters: fields, page_id. Required: fields, 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_fill_form: 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_fill_form 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_fill_form 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_fill_form. 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_fill_form 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