Get comprehensive traffic sources overview and summary report.
AI agents call sources_summary 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 and queries analytics data about traffic sources. It performs no data creation, modification, deletion, code execution, or financial operations. The 'Get' verb and the context of a Yandex Metrika analytics server confirm this is a read-only data retrieval tool with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'sources_summary' and description 'Get comprehensive traffic sources overview and summary report' indicate data retrieval without modification. The verb 'Get' and the nature of analytics reporting (traffic sources overview) are read-only operations.
Attacks that exploit this kind of access
Get comprehensive traffic sources overview and summary report. 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_summary: 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_summary 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_summary 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_summary. 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_summary 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 →