get-resume-negotiations-history

History of responses/invitations for a resume

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

What get-resume-negotiations-history does on HeadHunter API MCP Server

AI agents call get-resume-negotiations-history to retrieve information from HeadHunter API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get-resume-negotiations-history needs a policy

This tool retrieves negotiation history (responses and invitations) associated with a resume. It queries existing data without creating, modifying, deleting, or executing actions. The blast radius of misuse is minimal—an attacker could view negotiation history they shouldn't access, a privacy/confidentiality concern, but cannot alter employment records or commit to actions. This is a standard Read operation.

From the tool's definition Tool name 'get-resume-negotiations-history' with description 'History of responses/invitations for a resume' indicates retrieval of historical data with no modification capability. The 'get-' prefix and 'history' context signal a read-only query operation.

Questions about get-resume-negotiations-history

What does the get-resume-negotiations-history tool do? +

History of responses/invitations for a resume. It is categorised as a Read tool in the HeadHunter API MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-resume-negotiations-history? +

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

get-resume-negotiations-history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get-resume-negotiations-history? +

Yes. Add a rate_limit block to the get-resume-negotiations-history 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 get-resume-negotiations-history completely? +

Set action: deny in the PolicyLayer policy for get-resume-negotiations-history. 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 get-resume-negotiations-history? +

get-resume-negotiations-history 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.