hires_delete_candidate
Permanently delete a candidate by ID or alias.
This record as markdown: /tools/com-100hires-100hires/hires-delete-candidate.md
What hires_delete_candidate does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_delete_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). |
Parameters from the server's own tool schema.
Why hires_delete_candidate is rated Critical
This tool irreversibly removes candidate records from the recruitment system. While not financial in nature, permanent deletion of candidate data cannot be undone and represents a destructive action with potentially significant business impact (loss of recruitment history, candidate information, etc.). The high severity reflects the irreversible nature and the sensitive HR/recruitment context.
From the tool's definition Tool name contains 'delete' and description states 'Permanently delete a candidate by ID or alias.' The word 'Permanently' indicates an irreversible action.
Attacks that exploit this kind of access
The rule that runs hires_delete_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_delete_candidate, this is the rule to start with:
hires_delete_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_delete_candidate call is checked against it from then on.
Questions about hires_delete_candidate
Permanently delete a candidate by ID or alias. 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_candidate accepts 1 parameter: id. 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_delete_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_delete_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_delete_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_delete_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_delete_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