Get company metadata from Yandex Maps.
AI agents call get_company_info to retrieve information from Ya Reviews without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available company metadata from Yandex Maps. It performs a query operation that returns data without creating, modifying, deleting, or executing any operations. The lack of API key requirement and headless browser usage are implementation details that do not elevate the risk category. Misuse would result in data exfiltration or scraping, which is a low-severity read-only risk.
From the tool's definition Tool name 'get_company_info' and description 'Get company metadata from Yandex Maps' indicate data retrieval with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Get company metadata from Yandex Maps. It is categorised as a Read tool in the Ya Reviews MCP Server, which means it retrieves data without modifying state.
Register the Ya Reviews MCP server in PolicyLayer and add a rule for get_company_info: 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 Reviews. Nothing to install.
get_company_info 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_company_info 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_company_info. 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_company_info is provided by the Ya Reviews MCP server (mrkhachaturov/ya-reviews-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 →