research
One-call web research: searches the web, renders the top hits in the real browser, and returns a GROUNDED, CITED answer ({answer, sources:[{n,title,url}]}). Falls back to the rendered sources if synthesis is unavailable. Free. Pass handle for governed tiers.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/research.md
What research does on Gateway
AI agents call research 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 |
|---|---|---|---|
query | string | Yes | the question to research |
handle | string | — | your registered handle (governs powerful tiers) |
max_pages | integer | — | pages to read + cite (1-5, default 3) |
Parameters from the server's own tool schema.
Why research is rated Low
This tool retrieves and synthesizes information from the web without side effects. It queries external data sources and returns structured answers with citations. The fallback behavior of returning rendered sources confirms read-only intent. The mention of a 'handle' parameter for governed tiers does not alter the fundamental read operation. No write, execute, destructive, or financial capability is present.
From the tool's definition Tool performs "web research", "searches the web", "renders the top hits", and "returns a GROUNDED, CITED answer" with sources. No data modification, deletion, code execution, or financial operations are described.
Attacks that exploit this kind of access
The rule that runs research 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 research, this is the rule to start with:
research 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 research call is checked against it from then on.
Questions about research
One-call web research: searches the web, renders the top hits in the real browser, and returns a GROUNDED, CITED answer ({answer, sources:[{n,title,url}]}). Falls back to the rendered sources if synthesis is unavailable. Free. Pass handle for governed tiers. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
research accepts 3 parameters: query, handle, max_pages. Required: query. 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 research: 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.
research 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 research 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 research. 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.
research 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