get_geographical_organic_traffic
AI agents call get_geographical_organic_traffic 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.
The 'get_' prefix combined with server purpose (analytics reporting) indicates this tool retrieves geographical and organic traffic metrics without modifying or executing operations. No destructive, financial, or code execution capabilities are evident. Empty description slightly reduces confidence but naming convention and sibling tool patterns strongly suggest read-only query functionality.
From the tool's definition Tool name 'get_geographical_organic_traffic' indicates data retrieval with 'get' prefix. Server context shows it is part of Yandex Metrika analytics, which provides traffic reports and analytics data.
Attacks that exploit this kind of access
get_geographical_organic_traffic. 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_geographical_organic_traffic: 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_geographical_organic_traffic 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_geographical_organic_traffic 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_geographical_organic_traffic. 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_geographical_organic_traffic 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 →