put-negotiations-collection-to-next-state

WHAT IT DOES

What put-negotiations-collection-to-next-state does on HeadHunter API MCP Server

AI agents use put-negotiations-collection-to-next-state 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 put-negotiations-collection-to-next-state needs a policy

This tool modifies the state of negotiations, responses, or invitations within the HeadHunter platform—a reversible Write operation. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). The blast radius is limited to negotiation workflow state changes, which can typically be reversed by advancing to another state or reverting.

From the tool's definition Tool name 'put-negotiations-collection-to-next-state' and description 'Actions with responses/invitations' indicate state transitions on negotiation objects (responses/invitations).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

put-negotiations-collection-to-next-state Rate-limited

put-negotiations-collection-to-next-state 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": {
    "put-negotiations-collection-to-next-state": {
      "limits": [
        {
          "counter": "put-negotiations-collection-to-next-state_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 put-negotiations-collection-to-next-state

What does the put-negotiations-collection-to-next-state tool do? +

Actions with responses/invitations. 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 put-negotiations-collection-to-next-state? +

Register the HeadHunter API MCP Server MCP server in PolicyLayer and add a rule for put-negotiations-collection-to-next-state: 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 put-negotiations-collection-to-next-state? +

put-negotiations-collection-to-next-state is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit put-negotiations-collection-to-next-state? +

Yes. Add a rate_limit block to the put-negotiations-collection-to-next-state 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 put-negotiations-collection-to-next-state completely? +

Set action: deny in the PolicyLayer policy for put-negotiations-collection-to-next-state. 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 put-negotiations-collection-to-next-state? +

put-negotiations-collection-to-next-state 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.