hide-active-response · HeadHunter API MCP Server MCP

WHAT IT DOES

What hide-active-response does on HeadHunter API MCP Server

AI agents use hide-active-response 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 hide-active-response needs a policy

Hiding a response modifies its visibility state but is likely reversible (can be unhidden). This is a Write operation affecting negotiation/application data. Severity is medium as misuse could hide important job responses from a user without their knowledge.

From the tool's definition 'Hide response' - hides an active response/application, which is a reversible modification of visibility state

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

hide-active-response Rate-limited

hide-active-response 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": {
    "hide-active-response": {
      "limits": [
        {
          "counter": "hide-active-response_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 hide-active-response

What does the hide-active-response tool do? +

Hide response. 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 hide-active-response? +

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

hide-active-response is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit hide-active-response? +

Yes. Add a rate_limit block to the hide-active-response 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 hide-active-response completely? +

Set action: deny in the PolicyLayer policy for hide-active-response. 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 hide-active-response? +

hide-active-response 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.