change-negotiation-action · HeadHunter API MCP Server MCP

WHAT IT DOES

What change-negotiation-action does on HeadHunter API MCP Server

AI agents use change-negotiation-action to create or update resources in HeadHunter API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your HeadHunter API MCP Server environment.

WHY IT NEEDS A POLICY

Why change-negotiation-action needs a policy

The tool performs actions on negotiations (responses/invitations), which represents modifying existing data or state on the platform. This is a Write operation as it changes negotiation records. The description is vague, which lowers confidence slightly. Severity is medium since misuse could affect job application negotiations but is likely reversible.

From the tool's definition 'Actions with collection response/invitation' — modifies negotiation state (response/invitation actions)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

change-negotiation-action Rate-limited

change-negotiation-action stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "change-negotiation-action": {
      "limits": [
        {
          "counter": "change-negotiation-action_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches HeadHunter API MCP Server, so you can run agents against it safely.

FAQ

Questions about change-negotiation-action

What does the change-negotiation-action tool do? +

Actions with collection response/invitation. It is categorised as a Write tool in the HeadHunter API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on change-negotiation-action? +

Register the HeadHunter API MCP Server MCP server in PolicyLayer and add a rule for change-negotiation-action: 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 change-negotiation-action? +

change-negotiation-action is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit change-negotiation-action? +

Yes. Add a rate_limit block to the change-negotiation-action 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 change-negotiation-action completely? +

Set action: deny in the PolicyLayer policy for change-negotiation-action. 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 change-negotiation-action? +

change-negotiation-action 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.