browser_type
Type text into an input field by CSS selector. Returns a screenshot after typing. Set clear=true to clear existing text first.
This record as markdown: /tools/io-github-kivanccakmak-yaver/browser-type.md
What browser_type does on Yaver
AI agents invoke browser_type to trigger actions in Yaver. 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 |
|---|---|---|---|
text | string | Yes | Text to type |
clear | boolean | — | Clear field before typing (default: false) |
selector | string | Yes | CSS selector of input field |
session_id | string | Yes | Session ID |
Parameters from the server's own tool schema.
Why browser_type is rated High
Typing into a browser input field is a browser automation action (Execute category). It interacts with live UI, can submit forms or alter application state depending on what is typed and where. The 'clear=true' option to overwrite existing text adds a write-like dimension, but the primary nature is executing a browser interaction.
From the tool's definition 'Type text into an input field by CSS selector' and 'Returns a screenshot after typing' — triggers a browser action (typing into a UI element) and captures state, constituting an external operation with side effects dependent on arguments.
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 Yaver, 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 Yaver, apply this rule, and every browser_type call is checked against it from then on.
Questions about browser_type
Type text into an input field by CSS selector. Returns a screenshot after typing. Set clear=true to clear existing text first. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_type accepts 4 parameters: text, clear, selector, session_id. Required: text, selector, session_id. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver 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 Yaver. 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 Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
Across the catalogue