Retrieve search phrases and browser information from traffic sources.
AI agents call sources_search_phrases 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 analytics metrics and search phrase data from Yandex Metrika, which are observational queries with no side effects. No data is modified, deleted, or executed. The blast radius of misuse is minimal—an AI agent could only over-query the API or access analytics data the authenticated user already has permission to view.
From the tool's definition Tool name 'sources_search_phrases' and description 'Retrieve search phrases and browser information from traffic sources' indicate data retrieval only.
Attacks that exploit this kind of access
Retrieve search phrases and browser information from traffic sources. 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 sources_search_phrases: 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.
sources_search_phrases 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 sources_search_phrases 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 sources_search_phrases. 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.
sources_search_phrases 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 →