web_search
Search the public web Search the public web through the normalized Web Search provider contract. HTTP: GET /v1/web/search
This record as markdown: /tools/com-replynodes-mcp/web-search.md
What web_search does on ReplyNodes
AI agents call web_search to retrieve information from ReplyNodes 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 |
|---|---|---|---|
date | string | — | Provider date filter. |
lang | string | — | Language code. |
site | string | — | Restrict results to a site or domain. |
text | string | Yes | Search query text. |
limit | integer | — | Maximum number of results; values outside 1..100 are rejected. |
start | integer | — | Zero-based result offset. |
region | string | — | Search region. |
engines | string | — | Comma-separated search engines. |
Parameters from the server's own tool schema.
Why web_search is rated Low
Retrieves publicly available search results with no side effects or data modification.
From the tool's definition Search the public web
Attacks that exploit this kind of access
The rule that runs web_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ReplyNodes, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For web_search, this is the rule to start with:
web_search 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 ReplyNodes, apply this rule, and every web_search call is checked against it from then on.
Questions about web_search
Search the public web Search the public web through the normalized Web Search provider contract. HTTP: GET /v1/web/search. It is categorised as a Read tool in the ReplyNodes MCP Server, which means it retrieves data without modifying state.
web_search accepts 8 parameters: date, lang, site, text, limit, start, region, engines. Required: text. The full parameter table on this page comes from the server's own tool schema.
Register the ReplyNodes MCP server in PolicyLayer and add a rule for web_search: 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 ReplyNodes. Nothing to install.
web_search 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_search 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_search. 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_search is provided by the ReplyNodes MCP server (https://mcp.replynodes.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ReplyNodes, and thousands of servers like it.
This server
Across the catalogue