Archiving vacancies
AI agents use add-vacancy-to-archive to create or update resources in HeadHunter API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HeadHunter API MCP Server environment.
This tool modifies the state of vacancy records by archiving them, which is a reversible write operation. While archiving removes vacancies from active listings, it does not permanently delete data and can typically be undone by unarchiving. The severity is medium because misuse could remove job postings from visibility, impacting recruiting operations, but the action is recoverable.
From the tool's definition Tool name 'add-vacancy-to-archive' and description 'Archiving vacancies' indicate a modification operation that moves vacancies to an archived state.
Attacks that exploit this kind of access
Archiving vacancies. It is categorised as a Write tool in the HeadHunter API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the HeadHunter API MCP Server MCP server in PolicyLayer and add a rule for add-vacancy-to-archive: 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.
add-vacancy-to-archive is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add-vacancy-to-archive 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 add-vacancy-to-archive. 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.
add-vacancy-to-archive 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 →