Fill a set of fields by label or selector (generic HTML forms).
AI agents invoke browser.fill_form to trigger actions in MCP Playwright Browser. 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.
browser.fill_form triggers browser automation actions that interact with external web forms. Filling forms can submit data to external systems, trigger workflows, create accounts, post content, or initiate transactions depending on what form is targeted. This is an external operation whose effects depend on the arguments provided, placing it in the Execute category.
From the tool's definition Fill a set of fields by label or selector (generic HTML forms)
Attacks that exploit this kind of access
Fill a set of fields by label or selector (generic HTML forms). It is categorised as a Execute tool in the MCP Playwright Browser MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Playwright Browser 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 MCP Playwright Browser. 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 MCP Playwright Browser MCP server (mhrnqaruni/mcp-playwright-browser). 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 →