Fills multiple form fields at once. Pass a dict of {selector: value} pairs.
AI agents use fill_form to create or update resources in Brave Browser MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Brave Browser MCP Server environment.
fill_form writes data into form fields in the browser. It modifies the state of the current page's form inputs, which is a write operation. It doesn't execute code or irreversibly delete data, but could be misused to submit sensitive information or fill credentials into malicious forms.
From the tool's definition 'Fills multiple form fields at once. Pass a dict of {selector: value} pairs.'
Attacks that exploit this kind of access
Fills multiple form fields at once. Pass a dict of {selector: value} pairs. It is categorised as a Write tool in the Brave Browser MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Brave Browser MCP Server MCP server in PolicyLayer and add a rule for 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 Brave Browser MCP Server. Nothing to install.
fill_form 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 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 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.
fill_form is provided by the Brave Browser MCP Server MCP server (slaveofgod1/brave-browser-mcp). 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 →