get_content_analytics_articles
AI agents call get_content_analytics_articles 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 data about articles (content analytics). Like its sibling tools (get_content_analytics_authors, get_content_analytics_categories, etc.), it queries Yandex Metrika for analytical insights with no side effects, no data modification, and no destructive capabilities. Read access to analytics data poses minimal risk in terms of blast radius from misuse.
From the tool's definition Tool name 'get_content_analytics_articles' follows the 'get_' prefix pattern consistent with other Read tools on this server (get_account_info, get_browsers_report, get_content_analytics_*).
Attacks that exploit this kind of access
get_content_analytics_articles. 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_content_analytics_articles: 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_content_analytics_articles 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_content_analytics_articles 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_content_analytics_articles. 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_content_analytics_articles 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 →