web_discover
Tier-0 front door: check whether a site offers an AGENT-NATIVE interface (llms.txt / OpenAPI / ai-plugin) and prefer it over scraping. Free.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/web-discover.md
What web_discover does on Gateway
AI agents call web_discover 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 | site to probe (http/https; SSRF-guarded) |
Parameters from the server's own tool schema.
Why web_discover is rated Low
web_discover performs passive discovery of published interface metadata (llms.txt, OpenAPI specs, ai-plugin files). It reads and returns information about what capabilities a target site exposes; it does not execute code, modify data, or trigger external side effects.
From the tool's definition Tool name and description indicate it 'check[s] whether a site offers' agent-native interfaces—a pure information retrieval operation. The description explicitly states it checks/discovers capabilities, not modifies or executes anything.
Risk signalsAccepts URL/endpoint input (url)
Attacks that exploit this kind of access
The rule that runs web_discover 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_discover, this is the rule to start with:
web_discover 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_discover call is checked against it from then on.
Questions about web_discover
Tier-0 front door: check whether a site offers an AGENT-NATIVE interface (llms.txt / OpenAPI / ai-plugin) and prefer it over scraping. Free. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
web_discover accepts 1 parameter: url. 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_discover: 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_discover 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_discover 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_discover. 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_discover 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