browse_links
All links on the current page [{text, href}]; same_site_only filters to the current host.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/browse-links.md
What browse_links does on Gateway
AI agents call browse_links to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
browser_id | string | Yes | from browse_open |
same_site_only | boolean | — | only links on the current host |
Parameters from the server's own tool schema.
Why browse_links is rated Low
This tool queries and returns structured data about hyperlinks present on a webpage. It performs no side effects, does not execute links, does not modify data, and does not delete anything. The same_site_only parameter is a read-time filter. This is a straightforward Read category tool with low severity since it only exposes publicly visible link metadata.
From the tool's definition Tool description states it retrieves 'All links on the current page' with filtering options. The verb 'browse' and the function of extracting link metadata ({text, href}) indicates data retrieval with no modification or execution of those links.
Attacks that exploit this kind of access
The rule that runs browse_links 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_links, this is the rule to start with:
browse_links is read-only, so it stays allowed. 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_links call is checked against it from then on.
Questions about browse_links
All links on the current page [{text, href}]; same_site_only filters to the current host. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
browse_links accepts 2 parameters: browser_id, same_site_only. Required: 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_links: 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_links is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the browse_links 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_links. 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_links 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.
This server
Across the catalogue