browse_open

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

High RISK CLASS

Category Execute

Parameters 60 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/browse-open.md

WHAT IT DOES

What browse_open does on Gateway

AI agents invoke browse_open 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
`url`	string	—	optional first URL to navigate on open
`mode`	string	—	default honest
`sign`	boolean	—	send a Web Bot Auth signed identity (Tier-0)
`proxy`	object	—	BYO proxy {server,username?,password?} (Tier-1, governed)
`handle`	string	—	your registered handle (governs powerful tiers)
`fingerprint`	object	—	BYO fingerprint overrides (ua/platform/viewport/...)

Parameters from the server's own tool schema.

RISK

Why browse_open is rated High

This tool launches a persistent, stateful browser session capable of logging in, filling forms, clicking through multi-page flows, and performing arbitrary web actions. It is an execution tool with broad web-automation capabilities. An AI agent misusing it could submit forms, authenticate as a user, trigger purchases, post content, or perform other high-impact web actions — hence high severity.

From the tool's definition Open a PERSISTENT browser session (cookies/login survive across calls) and get a browser_id to drive with browse_navigate/snapshot/click/type/fill/.../close. THIS is how you ACT on the web — log in, fill forms, click through multi-page flows

Risk signalsAccepts URL/endpoint input (url)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs browse_open 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_open, this is the rule to start with:

browse_open Rate-limited

browse_open 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "browse_open": {
      "limits": [
        {
          "counter": "browse_open_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every browse_open call is checked against it from then on.

FAQ

Questions about browse_open

What does the browse_open tool do? +

Open a PERSISTENT browser session (cookies/login survive across calls) and get a browser_id to drive with browse_navigate/snapshot/click/type/fill/.../close. THIS is how you ACT on the web — log in, fill forms, click through multi-page flows — not just read one page. Free. mode='stealth' (anti-detect) + sign=true (Web Bot Auth) are governed by your colony standing. Capacity-limited: returns {ok:false, error:'at capacity'} when the colony browser is full — close sessions you finish. 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.

What parameters does browse_open accept? +

browse_open accepts 6 parameters: url, mode, sign, proxy, handle, fingerprint. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on browse_open? +

Register the Gateway MCP server in PolicyLayer and add a rule for browse_open: 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.

What risk level is browse_open? +

browse_open is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit browse_open? +

Yes. Add a rate_limit block to the browse_open 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.

How do I block browse_open completely? +

Set action: deny in the PolicyLayer policy for browse_open. 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.

What MCP server provides browse_open? +

browse_open 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.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →