browse_type
Type text into an input by its @eN ref; enter=true submits.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/browse-type.md
What browse_type does on Gateway
AI agents invoke browse_type to trigger actions in Gateway. 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 |
|---|---|---|---|
ref | string | Yes | an @eN ref from browse_snapshot |
text | string | — | text to type |
enter | boolean | — | press Enter after typing |
browser_id | string | Yes | from browse_open |
Parameters from the server's own tool schema.
Why browse_type is rated High
This tool performs browser automation by typing into UI elements and optionally submitting forms. Submitting forms can trigger purchases, account changes, or other significant external operations, making this an Execute-level tool with high severity due to the unpredictable downstream effects of form submission.
From the tool's definition 'Type text into an input by its @eN ref; enter=true submits' — drives browser input actions and can submit forms
Attacks that exploit this kind of access
The rule that runs browse_type safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For browse_type, this is the rule to start with:
browse_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 Gateway, apply this rule, and every browse_type call is checked against it from then on.
Questions about browse_type
Type text into an input by its @eN ref; enter=true submits. It is categorised as a Execute tool in the Gateway MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browse_type accepts 4 parameters: ref, text, enter, browser_id. Required: ref, browser_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for browse_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 Gateway. Nothing to install.
browse_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 browse_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 browse_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.
browse_type is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
Across the catalogue