Search the web for information. Use when you need to find web pages, articles, or data. Providers: tavily (factual/citations), brave (privacy/operators), kagi (quality/operators), exa (AI-semantic), kagi_enrichment (specialized indexes). Brave/Kagi support query operators like site:, filetype:, l...
AI agents call web_search to retrieve information from Mcp Omnisearch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information from the web without side effects. It does not create, modify, delete, execute code, or move money. The query operators mentioned (site:, filetype:, lang:, before:, after:) are standard search filters that only narrow retrieval scope. No reversible or irreversible mutations are possible, making this a pure Read operation with minimal security risk if misused.
From the tool's definition Tool description explicitly states it "Search[es] the web for information" and "find[s] web pages, articles, or data" with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search the web for information. Use when you need to find web pages, articles, or data. Providers: tavily (factual/citations), brave (privacy/operators), kagi (quality/operators), exa (AI-semantic), kagi_enrichment (specialized indexes). Brave/Kagi support query operators like site:, filetype:, lang:, before:, after:. It is categorised as a Read tool in the Mcp Omnisearch MCP Server, which means it retrieves data without modifying state.
Register the Mcp Omnisearch 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 Mcp Omnisearch. 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 Mcp Omnisearch MCP server (mcp-omnisearch). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
web_search is one line of Mcp Omnisearch's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →