The list of metro stations in all cities
AI agents call get-metro-stations to retrieve information from HeadHunter API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of metro stations, which is read-only data with no side effects, no modifications, and no ability to affect systems or data. The information is public reference data. Classification as Read is appropriate, and severity is low given the non-sensitive nature of public transit information and absence of blast radius for misuse.
From the tool's definition Tool name 'get-metro-stations' and description 'The list of metro stations in all cities' indicate a retrieval operation that returns static reference data about public transit infrastructure.
Attacks that exploit this kind of access
The list of metro stations in all cities. It is categorised as a Read tool in the HeadHunter API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HeadHunter API MCP Server MCP server in PolicyLayer and add a rule for get-metro-stations: 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 HeadHunter API MCP Server. Nothing to install.
get-metro-stations 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-metro-stations 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-metro-stations. 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-metro-stations is provided by the HeadHunter API MCP Server MCP server (sargonpiraev/hh-mcp-server). 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 →