delete-employer-from-blacklisted

Deleting an employer from the blacklist

Server HeadHunter API MCP Server sargonpiraev/hh-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete-employer-from-blacklisted does on HeadHunter API MCP Server

AI agents call delete-employer-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.

Why delete-employer-from-blacklisted needs a policy

This tool irreversibly deletes blacklist records. While not as critical as deleting core user or financial data, unauthorized removal of an employer from a blacklist could enable fraudulent hiring practices by removing visibility of problematic employers. The action is non-reversible and alters security/trust boundaries, warranting Destructive classification with high severity.

From the tool's definition Tool name 'delete-employer-from-blacklisted' and description 'Deleting an employer from the blacklist' explicitly indicate permanent removal of data from a blacklist. The action cannot be reversed without re-adding the employer.

Questions about delete-employer-from-blacklisted

What does the delete-employer-from-blacklisted tool do? +

Deleting an employer 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.

How do I enforce a policy on delete-employer-from-blacklisted? +

Register the HeadHunter API MCP Server MCP server in PolicyLayer and add a rule for delete-employer-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.

What risk level is delete-employer-from-blacklisted? +

delete-employer-from-blacklisted is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-employer-from-blacklisted? +

Yes. Add a rate_limit block to the delete-employer-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.

How do I block delete-employer-from-blacklisted completely? +

Set action: deny in the PolicyLayer policy for delete-employer-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.

What MCP server provides delete-employer-from-blacklisted? +

delete-employer-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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.