crow_browser_fill_form
Fill form fields with human-like typing. Accepts a map of selector -> value pairs.
This record as markdown: /tools/kh0pper-crow/crow-browser-fill-form.md
What crow_browser_fill_form does on Crow
AI agents invoke crow_browser_fill_form to trigger actions in Crow. 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.
Why crow_browser_fill_form is rated High
This tool performs browser automation by interacting with form fields in a web browser, simulating human input. It triggers external operations whose effects depend on the arguments provided (selectors and values). Depending on what form is filled and submitted, this could have significant downstream effects — submitting credentials, personal data, orders, etc.
From the tool's definition Fill form fields with human-like typing. Accepts a map of selector -> value pairs.
Attacks that exploit this kind of access
The rule that runs crow_browser_fill_form safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_browser_fill_form, this is the rule to start with:
crow_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 Crow, apply this rule, and every crow_browser_fill_form call is checked against it from then on.
Questions about crow_browser_fill_form
Fill form fields with human-like typing. Accepts a map of selector -> value pairs. It is categorised as a Execute tool in the Crow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Crow MCP server in PolicyLayer and add a rule for crow_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 Crow. Nothing to install.
crow_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 crow_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 crow_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.
crow_browser_fill_form is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue