Deleting a vacancy from the blacklist
AI agents call delete-vacancy-from-blacklisted to permanently remove resources in HeadHunter API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes a vacancy from a blacklist, which is a deletion action. While not catastrophic (it could be seen as reversible if the vacancy can be re-added), the operation itself is a delete/remove action. However, since adding to blacklist is a separate action and this removal could expose the user to unwanted vacancies again, it fits best under Destructive.
From the tool's definition 'Deleting a vacancy from the blacklist' — the action is a deletion/removal operation
Attacks that exploit this kind of access
Deleting a vacancy from the blacklist. It is categorised as a Destructive tool in the HeadHunter API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the HeadHunter API MCP Server MCP server in PolicyLayer and add a rule for delete-vacancy-from-blacklisted: 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.
delete-vacancy-from-blacklisted is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete-vacancy-from-blacklisted 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 delete-vacancy-from-blacklisted. 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.
delete-vacancy-from-blacklisted 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 →