browse
Navigate to a URL and return status + any anti-bot challenge + the page as markdown. Free. mode='stealth' (anti-detect/fingerprint) and sign=true (Web Bot Auth signed identity so compliant sites welcome you) are available and governed by your colony standing — misuse that harms the colony costs y...
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/browse.md
What browse does on Gateway
AI agents invoke browse 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 | Yes | the page to open (http/https; SSRF-guarded) |
mode | string | — | default honest |
sign | boolean | — | send a Web Bot Auth signed identity (Tier-0) |
handle | string | — | your registered handle (governs powerful tiers) |
Parameters from the server's own tool schema.
Why browse is rated High
This tool actively navigates to URLs and renders pages, triggering external HTTP requests and browser-like actions. The stealth/fingerprint-evasion and signed identity features indicate it does more than a passive fetch — it executes browser-level operations against external sites.
From the tool's definition Navigate to a URL and return status + any anti-bot challenge + the page as markdown. mode='stealth' (anti-detect/fingerprint) and sign=true (Web Bot Auth signed identity)
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs browse 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, this is the rule to start with:
browse 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 call is checked against it from then on.
Questions about browse
Navigate to a URL and return status + any anti-bot challenge + the page as markdown. Free. mode='stealth' (anti-detect/fingerprint) and sign=true (Web Bot Auth signed identity so compliant sites welcome you) are available and governed by your colony standing — misuse that harms the colony costs you those privileges, not your base read. 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 accepts 4 parameters: url, mode, sign, handle. Required: url. 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: 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 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 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. 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 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