send-code-for-verify-phone-in-resume

WHAT IT DOES

What send-code-for-verify-phone-in-resume does on HeadHunter API MCP Server

AI agents use send-code-for-verify-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 send-code-for-verify-phone-in-resume needs a policy

This tool initiates a phone verification workflow by sending a code, which modifies the verification state of a resume and creates a transient but reversible interaction (the code can expire or be resent). It is not a read-only operation (it triggers an outbound action), nor is it destructive or financial. It falls into Write because it creates/modifies verification data and state.

From the tool's definition Tool description: 'Send verification code to the phone number on CV' — this action sends a verification code to a phone number, creating a temporary verification state/record in the system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

send-code-for-verify-phone-in-resume Rate-limited

send-code-for-verify-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": {
    "send-code-for-verify-phone-in-resume": {
      "limits": [
        {
          "counter": "send-code-for-verify-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 send-code-for-verify-phone-in-resume

What does the send-code-for-verify-phone-in-resume tool do? +

Send verification code to the phone number on CV. 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 send-code-for-verify-phone-in-resume? +

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

send-code-for-verify-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 send-code-for-verify-phone-in-resume? +

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

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

send-code-for-verify-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.