get_page_performance
AI agents call get_page_performance 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 performance metrics for pages from Yandex Metrika analytics platform. No description provided, but contextual evidence from server purpose (enabling access to analytics reports) and sibling tools (all 'get_*' report retrieval functions) indicates read-only data access. Retrieving analytics does not modify, execute external operations, or impact financial systems.
From the tool's definition Tool name 'get_page_performance' and sibling tools (get_account_info, get_browsers_report, get_content_analytics_*) all retrieve analytics data without modification. Description is empty, but naming pattern and server purpose indicate data retrieval.
Attacks that exploit this kind of access
get_page_performance. 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_page_performance: 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_page_performance 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_page_performance 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_page_performance. 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_page_performance 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 →