Deleting a manager
AI agents call delete-employer-manager 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 irreversibly removes an employer manager account or record from the HeadHunter platform. Deletion cannot be undone and permanently eliminates the manager's access and associated data. While not directly financial or executing arbitrary code, the removal of an administrative user with platform access represents a significant destructive action that could disrupt employer operations and access control.
From the tool's definition Tool name 'delete-employer-manager' explicitly uses the verb 'delete'; description states 'Deleting a manager'
Attacks that exploit this kind of access
Deleting a manager. 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-employer-manager: 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-employer-manager 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-employer-manager 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-employer-manager. 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-employer-manager 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 →