web_search
Search the web for current information, news, facts, prices, or events. Use this when the user asks about something that requires up-to-date information from the internet, or when internal knowledge base doesn't have the answer. Examples: recent news, stock prices, weather, product information, c...
This record as markdown: /tools/io-github-saloprj-dialogbrain/web-search.md
What web_search does on Dialogbrain
AI agents call web_search to retrieve information from Dialogbrain 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 | Search query - what to search for on the web. |
num_results | integer | — | Number of results to return (1-10). |
search_type | string | — | Type of search: 'search' for general web, 'news' for news articles. |
Parameters from the server's own tool schema.
Why web_search is rated Low
This is a query/search tool that retrieves data from external sources without side effects. It performs a read-only operation typical of information lookup functionality. No data is created, modified, deleted, or executed through this tool—it simply fetches and returns information, making it a classic Read category tool.
From the tool's definition Tool description states it 'Search[es] the web for current information, news, facts, prices, or events' with no mention of modifying, deleting, or executing operations.
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 Dialogbrain, 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 Dialogbrain, apply this rule, and every web_search call is checked against it from then on.
Questions about web_search
Search the web for current information, news, facts, prices, or events. Use this when the user asks about something that requires up-to-date information from the internet, or when internal knowledge base doesn't have the answer. Examples: recent news, stock prices, weather, product information, current events. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.
web_search accepts 3 parameters: query, num_results, search_type. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Dialogbrain 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 Dialogbrain. 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 Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dialogbrain, and thousands of servers like it.
This server
Across the catalogue