get_content_analytics_authors
AI agents call get_content_analytics_authors 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 content analytics information (authors) from Yandex Metrika, consistent with the server's purpose of enabling access to analytics reports. No modification, deletion, code execution, or financial operations are indicated. The 'get_' prefix and analytics context confirm read-only data retrieval with no side effects.
From the tool's definition Tool name 'get_content_analytics_authors' indicates retrieval of content analytics data; server context shows all sibling tools (get_browsers_report, get_content_analytics_*) are read-only analytics queries; description is empty but naming pattern and server…
Attacks that exploit this kind of access
get_content_analytics_authors. 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_authors: 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_authors 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_authors 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_authors. 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_authors 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 →