Search for vacancies related to a vacancy
AI agents call get-vacancies-related-to-vacancy 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 and searches vacancy data with no side effects. It is a read-only query operation that returns related job postings based on a reference vacancy. No data is created, modified, deleted, or used to trigger external actions.
From the tool's definition Tool name 'get-vacancies' and description 'Search for vacancies' indicate data retrieval. No modification, deletion, execution, or financial action occurs.
Attacks that exploit this kind of access
Search for vacancies related to a vacancy. 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-vacancies-related-to-vacancy: 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-vacancies-related-to-vacancy 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-vacancies-related-to-vacancy 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-vacancies-related-to-vacancy. 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-vacancies-related-to-vacancy 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 →