hires_delete_job_webhook
Delete a job webhook subscription by ID. Use for cleanup, rotation, and endpoint migration.
This record as markdown: /tools/com-100hires-100hires/hires-delete-job-webhook.md
What hires_delete_job_webhook does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_delete_job_webhook to permanently remove resources in 100Hires - AI ATS & Recruitment Software, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | number | Yes | Job ID (numeric) or alias |
webhook_id | number | Yes | Webhook ID to delete |
Parameters from the server's own tool schema.
Why hires_delete_job_webhook is rated Critical
This tool permanently removes a webhook subscription, which is an irreversible operation. Although webhooks are configuration rather than business-critical records, their deletion could disrupt automation workflows, event notifications, and integrations tied to job events in the ATS. The blast radius is moderate to high depending on how many systems depend on that webhook.
From the tool's definition 'Delete a job webhook subscription by ID' — the verb 'Delete' combined with irreversible removal of a webhook resource indicates data destruction. Webhook subscriptions, once deleted, cannot be recovered without manual recreation.
Attacks that exploit this kind of access
The rule that runs hires_delete_job_webhook safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 100Hires - AI ATS & Recruitment Software, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hires_delete_job_webhook, this is the rule to start with:
hires_delete_job_webhook is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 100Hires - AI ATS & Recruitment Software, apply this rule, and every hires_delete_job_webhook call is checked against it from then on.
Questions about hires_delete_job_webhook
Delete a job webhook subscription by ID. Use for cleanup, rotation, and endpoint migration. It is categorised as a Destructive tool in the 100Hires - AI ATS & Recruitment Software MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
hires_delete_job_webhook accepts 2 parameters: id, webhook_id. Required: id, webhook_id. The full parameter table on this page comes from the server's own tool schema.
Register the 100Hires - AI ATS & Recruitment Software MCP server in PolicyLayer and add a rule for hires_delete_job_webhook: 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 100Hires - AI ATS & Recruitment Software. Nothing to install.
hires_delete_job_webhook 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 hires_delete_job_webhook 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 hires_delete_job_webhook. 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.
hires_delete_job_webhook is provided by the 100Hires - AI ATS & Recruitment Software MCP server (https://mcp.100hires.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 100Hires - AI ATS & Recruitment Software, and thousands of servers like it.
This server
Across the catalogue