delete-resume-visibility-list

WHAT IT DOES

What delete-resume-visibility-list does on HeadHunter API MCP Server

AI agents call delete-resume-visibility-list 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 IT NEEDS A POLICY

Why delete-resume-visibility-list needs a policy

The tool clears/deletes a visibility list for a resume, which is an irreversible bulk deletion of access control data. This falls under Destructive as it permanently removes visibility settings that control who can see a resume, with high severity since misuse could expose or hide a resume from unintended audiences.

From the tool's definition 'delete-resume-visibility-list' and description 'Clearing the visibility list' — clearing implies irreversible removal of all entries in the resume visibility list

Attacks that exploit this kind of access

Questions about delete-resume-visibility-list

What does the delete-resume-visibility-list tool do? +

Clearing the visibility list. 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-resume-visibility-list? +

Register the HeadHunter API MCP Server MCP server in PolicyLayer and add a rule for delete-resume-visibility-list: 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-resume-visibility-list? +

delete-resume-visibility-list 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-resume-visibility-list? +

Yes. Add a rate_limit block to the delete-resume-visibility-list 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-resume-visibility-list completely? +

Set action: deny in the PolicyLayer policy for delete-resume-visibility-list. 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-resume-visibility-list? +

delete-resume-visibility-list 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.