Vacancy prolongation
AI agents use vacancy-prolongation 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.
Prolonging a vacancy extends its expiration date/active period on the platform. This is a reversible modification of an existing resource (the vacancy's duration), making it a Write operation. It does not delete data or execute arbitrary code. The description is minimal, lowering confidence slightly, but the term 'prolongation' clearly implies extending/updating a time-bound resource.
From the tool's definition 'Vacancy prolongation' - extends the active period of a vacancy listing
Attacks that exploit this kind of access
Vacancy prolongation. 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 vacancy-prolongation: 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.
vacancy-prolongation 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 vacancy-prolongation 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 vacancy-prolongation. 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.
vacancy-prolongation 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 →