get_search_engines_data
AI agents call get_search_engines_data to retrieve information from Ya Metrics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves search engine traffic analytics from Yandex Metrika—a read-only data query with no side effects, no execution of code or commands, and no data modification or deletion. The risk is low because misuse would only expose analytics data the account holder already possesses.
From the tool's definition Tool name 'get_search_engines_data' indicates data retrieval. Server description confirms this is an analytics tool for accessing 'traffic, content, demographics, conversion, e-commerce, and drill-down reports.' The 'get_' prefix and sibling tools (all named…
Attacks that exploit this kind of access
get_search_engines_data. It is categorised as a Read tool in the Ya Metrics MCP Server, which means it retrieves data without modifying state.
Register the Ya Metrics MCP server in PolicyLayer and add a rule for get_search_engines_data: 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 Ya Metrics. Nothing to install.
get_search_engines_data 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 get_search_engines_data 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 get_search_engines_data. 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.
get_search_engines_data is provided by the Ya Metrics MCP server (mrkhachaturov/ya-metrics-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 →