web_read
Read a web page the way fetch can't: render the REAL (JavaScript/SPA) page in a headless browser and return clean readability markdown. Free. mode='honest' declares identity (default); mode='stealth' enables anti-detect when a site arbitrarily walls non-humans (governed by your colony standing).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/web-read.md
What web_read does on Gateway
AI agents call web_read 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 |
|---|---|---|---|
url | string | Yes | the page to read (http/https; SSRF-guarded) |
mode | string | — | default honest |
handle | string | — | your registered handle (governs powerful tiers) |
Parameters from the server's own tool schema.
Why web_read is rated Low
This tool retrieves and renders web content without side effects. While it operates a headless browser (which could theoretically execute code), the stated purpose is purely to read and extract content. The 'stealth' mode for bypassing detection is a secondary concern but doesn't elevate the primary function from Read.
From the tool's definition Tool description explicitly states it 'Read[s] a web page' and 'return[s] clean readability markdown' with no modification, deletion, or execution capabilities. The 'mode' parameter controls disclosure behavior, not the fundamental read-only nature.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs web_read 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 web_read, this is the rule to start with:
web_read 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 web_read call is checked against it from then on.
Questions about web_read
Read a web page the way fetch can't: render the REAL (JavaScript/SPA) page in a headless browser and return clean readability markdown. Free. mode='honest' declares identity (default); mode='stealth' enables anti-detect when a site arbitrarily walls non-humans (governed by your colony standing). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
web_read accepts 3 parameters: url, mode, 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 web_read: 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.
web_read 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 web_read 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 web_read. 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.
web_read 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