search_yandex
AI agents call search_yandex to retrieve information from Web Search Neo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Web search tools are read-only operations that retrieve and return publicly available search results without modifying, executing code, or causing irreversible changes. Even though the tool's own description is empty, the server context and sibling tool patterns clearly indicate this is a data retrieval operation.
From the tool's definition Tool named 'search_yandex' on a server described as enabling 'searching the web via DuckDuckGo and Yandex'; sibling tools are 'fetch_page_links', 'fetch_url_text', 'get_current_time_and_region', and 'search_duckduckgo', all retrieval operations with no side…
Attacks that exploit this kind of access
search_yandex. It is categorised as a Read tool in the Web Search Neo MCP Server, which means it retrieves data without modifying state.
Register the Web Search Neo MCP server in PolicyLayer and add a rule for search_yandex: 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 Web Search Neo. Nothing to install.
search_yandex 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 search_yandex 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 search_yandex. 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.
search_yandex is provided by the Web Search Neo MCP server (neoxider/web-search-neo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →