Vacancy visitors
AI agents call get-vacancy-visitors 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 information about who has visited a vacancy posting. It queries existing data with no side effects—it does not create, modify, delete, or execute any actions. The operation is informational only, making it a Read category tool with low severity since unauthorized access to visitor analytics has limited blast radius compared to other capability categories.
From the tool's definition Tool name 'get-vacancy-visitors' and description 'Vacancy visitors' indicate a retrieval/query operation. The 'get-' prefix is a standard convention for read operations that fetch data without modification.
Attacks that exploit this kind of access
Vacancy visitors. 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-vacancy-visitors: 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-vacancy-visitors 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-vacancy-visitors 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-vacancy-visitors. 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-vacancy-visitors 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 →