move-saved-resume-search · HeadHunter API MCP Server MCP

WHAT IT DOES

What move-saved-resume-search does on HeadHunter API MCP Server

AI agents use move-saved-resume-search 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 move-saved-resume-search needs a policy

This tool modifies the state of a saved search resource by transferring it between managers, constituting a write operation. It is reversible (the search can be moved back), so it does not qualify as Destructive.

From the tool's definition Tool name 'move-saved-resume-search' and description 'Moving saved resumes search to other manager' indicate modification of search ownership/assignment across managers.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

move-saved-resume-search Rate-limited

move-saved-resume-search 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": {
    "move-saved-resume-search": {
      "limits": [
        {
          "counter": "move-saved-resume-search_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 move-saved-resume-search

What does the move-saved-resume-search tool do? +

Moving saved resumes search to other manager. 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 move-saved-resume-search? +

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

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

Can I rate-limit move-saved-resume-search? +

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

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

move-saved-resume-search 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.