hires_disqualify_candidate
Disqualify a candidate from all active applications. Optionally provide rejection reason IDs. Returns affected application IDs.
This record as markdown: /tools/com-100hires-100hires/hires-disqualify-candidate.md
What hires_disqualify_candidate does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_disqualify_candidate 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 | Candidate ID (integer) or alias (string). |
reasons | array | — | Array of rejection reason IDs from GET /taxonomy/rejection-reasons. |
Parameters from the server's own tool schema.
Why hires_disqualify_candidate is rated Critical
Disqualifying a candidate from all active applications is a significant irreversible action that removes them from consideration across the board. While it may technically be reversible in the system, the practical effect of disqualifying a candidate is permanent from a recruitment standpoint and affects all active applications simultaneously, making it high blast radius.
From the tool's definition Disqualify a candidate from all active applications
Attacks that exploit this kind of access
The rule that runs hires_disqualify_candidate 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_disqualify_candidate, this is the rule to start with:
hires_disqualify_candidate 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_disqualify_candidate call is checked against it from then on.
Questions about hires_disqualify_candidate
Disqualify a candidate from all active applications. Optionally provide rejection reason IDs. Returns affected application IDs. 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_disqualify_candidate accepts 2 parameters: id, reasons. Required: 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_disqualify_candidate: 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_disqualify_candidate 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_disqualify_candidate 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_disqualify_candidate. 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_disqualify_candidate 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