edit-current-user-info · HeadHunter API MCP Server MCP

WHAT IT DOES

What edit-current-user-info does on HeadHunter API MCP Server

AI agents use edit-current-user-info 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 edit-current-user-info needs a policy

The tool creates or modifies data reversibly (Write category). While it affects the authorized user's information, the action is reversible through subsequent edits. Severity is high because user profile data is sensitive (employment/professional information on a job platform), and misuse could lead to account compromise, identity spoofing, or reputational damage.

From the tool's definition Tool name 'edit-current-user-info' combined with description 'Editing information on the authorized user' indicates modification of user profile data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

edit-current-user-info Rate-limited

edit-current-user-info 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": {
    "edit-current-user-info": {
      "limits": [
        {
          "counter": "edit-current-user-info_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 edit-current-user-info

What does the edit-current-user-info tool do? +

Editing information on the authorized user. 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 edit-current-user-info? +

Register the HeadHunter API MCP Server MCP server in PolicyLayer and add a rule for edit-current-user-info: 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 edit-current-user-info? +

edit-current-user-info is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit edit-current-user-info? +

Yes. Add a rate_limit block to the edit-current-user-info 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 edit-current-user-info completely? +

Set action: deny in the PolicyLayer policy for edit-current-user-info. 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 edit-current-user-info? +

edit-current-user-info 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.