History of resume views
AI agents call get-resume-view-history 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 view history metadata associated with resumes—a read-only operation that returns existing data without creating, modifying, deleting, or executing actions. While the data may be sensitive (revealing who viewed a resume and when), the tool itself performs no side effects and poses minimal risk if misused by an AI agent, as it only exposes information already recorded in the system.
From the tool's definition Tool name 'get-resume-view-history' and description 'History of resume views' indicate retrieval of historical data without modification. The 'get-' prefix and 'history' keyword confirm this is a query/retrieval operation.
Attacks that exploit this kind of access
History of resume views. 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-resume-view-history: 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-resume-view-history 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-resume-view-history 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-resume-view-history. 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-resume-view-history 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 →