update-resume-profile · HeadHunter API MCP Server MCP

WHAT IT DOES

What update-resume-profile does on HeadHunter API MCP Server

AI agents use update-resume-profile 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-resume-profile needs a policy

This tool modifies candidate profile data reversibly—resume information can be edited multiple times and is not permanently deleted. It qualifies as Write rather than Read (retrieves data) or Destructive (irreversible deletion).

From the tool's definition update-resume-profile: 'Обновление резюме-профиля соискателя' (Update candidate resume-profile). The verb 'update' combined with 'resume-profile' indicates modification of existing candidate profile data on the HeadHunter platform.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update-resume-profile Rate-limited

update-resume-profile 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-resume-profile": {
      "limits": [
        {
          "counter": "update-resume-profile_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-resume-profile

What does the update-resume-profile tool do? +

Обновление резюме-профиля соискателя. 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-resume-profile? +

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

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

Can I rate-limit update-resume-profile? +

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

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

update-resume-profile 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.