post-webhook-subscription · HeadHunter API MCP Server MCP

WHAT IT DOES

What post-webhook-subscription does on HeadHunter API MCP Server

AI agents use post-webhook-subscription 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 post-webhook-subscription needs a policy

This tool creates or modifies webhook subscriptions, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). The severity is medium because misconfigured webhooks could expose sensitive data or cause notification spam, but the blast radius is limited compared to more dangerous operations.

From the tool's definition Tool name 'post-webhook-subscription' indicates a POST operation that creates a webhook subscription for notifications. This is a write operation that establishes a new persistent configuration on the platform.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

post-webhook-subscription Rate-limited

post-webhook-subscription 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": {
    "post-webhook-subscription": {
      "limits": [
        {
          "counter": "post-webhook-subscription_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 post-webhook-subscription

What does the post-webhook-subscription tool do? +

Subscription to notifications. 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 post-webhook-subscription? +

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

post-webhook-subscription is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit post-webhook-subscription? +

Yes. Add a rate_limit block to the post-webhook-subscription 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 post-webhook-subscription completely? +

Set action: deny in the PolicyLayer policy for post-webhook-subscription. 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 post-webhook-subscription? +

post-webhook-subscription 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.