update-applicant-comment · HeadHunter API MCP Server MCP

WHAT IT DOES

What update-applicant-comment does on HeadHunter API MCP Server

AI agents use update-applicant-comment 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 update-applicant-comment needs a policy

This tool modifies existing data reversibly by updating an applicant comment. It is a Write operation as it creates or modifies data without deletion or irreversible effects. Severity is medium because it affects communication records and could impact hiring decisions if maliciously modified, but the blast radius is limited to comment text rather than core employment records or financial commitments.

From the tool's definition Tool name 'update-applicant-comment' and description 'Update a comment' indicate modification of existing data (applicant comments) in the HeadHunter job platform.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-applicant-comment Rate-limited

update-applicant-comment 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": {
    "update-applicant-comment": {
      "limits": [
        {
          "counter": "update-applicant-comment_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 update-applicant-comment

What does the update-applicant-comment tool do? +

Update a comment. 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 update-applicant-comment? +

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

update-applicant-comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update-applicant-comment? +

Yes. Add a rate_limit block to the update-applicant-comment 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 update-applicant-comment completely? +

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

update-applicant-comment 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.