Delete a subscription on notifications
AI agents call cancel-webhook-subscription to permanently remove resources in HeadHunter API MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling/deleting a webhook subscription is an irreversible destructive action that removes the notification channel. While it can potentially be recreated, the deletion itself is not undone and could disrupt integrations relying on those notifications.
From the tool's definition 'Delete a subscription on notifications' — permanently removes a webhook subscription
Attacks that exploit this kind of access
Delete a subscription on notifications. It is categorised as a Destructive tool in the HeadHunter API MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the HeadHunter API MCP Server MCP server in PolicyLayer and add a rule for cancel-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.
cancel-webhook-subscription is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cancel-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.
Set action: deny in the PolicyLayer policy for cancel-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.
cancel-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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →