Directory of employer's addresses
AI agents call get-employer-addresses 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 or queries employer address information from the HeadHunter platform. It has no side effects—it does not create, modify, delete, or execute operations. The action is purely read-based data retrieval, which falls squarely into the Read category with low severity since address data is generally non-sensitive business information.
From the tool's definition Tool name 'get-employer-addresses' and description 'Directory of employer's addresses' indicate a retrieval operation that queries existing employer address data without modification or deletion.
Attacks that exploit this kind of access
Directory of employer's addresses. 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-employer-addresses: 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-employer-addresses 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-employer-addresses 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-employer-addresses. 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-employer-addresses 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 →