Get popular and related search queries for a keyword using Yandex Wordstat.
AI agents call wordstat_get_top to retrieve information from Yandex Searchapi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple statistical lookup to retrieve search query information. It has no side effects, cannot modify or delete data, does not execute arbitrary code, and does not involve financial transactions. The blast radius of misuse is minimal—an attacker could only gather keyword intelligence, which is informational in nature. Classification as 'Read' is appropriate.
From the tool's definition Tool retrieves "popular and related search queries" via Yandex Wordstat—a query/lookup operation with no modification, deletion, or code execution. The verb 'get' and the read-only nature of keyword statistics confirm this is data retrieval.
Attacks that exploit this kind of access
Get popular and related search queries for a keyword using Yandex Wordstat. It is categorised as a Read tool in the Yandex Searchapi MCP Server, which means it retrieves data without modifying state.
Register the Yandex Searchapi MCP server in PolicyLayer and add a rule for wordstat_get_top: 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 Yandex Searchapi. Nothing to install.
wordstat_get_top 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 wordstat_get_top 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 wordstat_get_top. 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.
wordstat_get_top is provided by the Yandex Searchapi MCP server (shufl9dka/yandex-searchapi-mcp). 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 →