confirm-phone-in-resume · HeadHunter API MCP Server MCP

WHAT IT DOES

What confirm-phone-in-resume does on HeadHunter API MCP Server

AI agents use confirm-phone-in-resume 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 confirm-phone-in-resume needs a policy

This tool performs a verification action that updates the confirmation status of a phone number in a resume—a reversible modification to user profile data. It is Write rather than Execute because it appears to be a targeted verification workflow rather than arbitrary code/command execution.

From the tool's definition Tool name 'confirm-phone-in-resume' and description 'Verify phone with a code' indicate a state-changing operation that modifies resume data by confirming/validating a phone number.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confirm-phone-in-resume Rate-limited

confirm-phone-in-resume 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": {
    "confirm-phone-in-resume": {
      "limits": [
        {
          "counter": "confirm-phone-in-resume_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 confirm-phone-in-resume

What does the confirm-phone-in-resume tool do? +

Verify phone with a code. 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 confirm-phone-in-resume? +

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

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

Can I rate-limit confirm-phone-in-resume? +

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

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

confirm-phone-in-resume 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.