Regions and cities
AI agents call get-salary-salary-areas 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 reference data (geographic regions and cities) that supports salary information lookups. It has no side effects, does not modify data, and poses minimal risk. It is a simple lookup/query operation typical of read operations.
From the tool's definition Tool name 'get-salary-salary-areas' with description 'Regions and cities' indicates data retrieval of geographic/location information used for salary data context.
Attacks that exploit this kind of access
Regions and 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-salary-salary-areas: 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-salary-salary-areas 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-salary-salary-areas 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-salary-salary-areas. 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-salary-salary-areas 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 →