hires_update_candidate
Update candidate fields, profile answers, and optional resume text. Used for bi-directional sync from ATS, CRM, sourcing, or enrichment tools. When the user provides an attached resume, parse it yourself from chat context and pass via resume_text — do not inline binary data.
This record as markdown: /tools/com-100hires-100hires/hires-update-candidate.md
What hires_update_candidate does on 100Hires - AI ATS & Recruitment Software
AI agents use hires_update_candidate to create or update resources in 100Hires - AI ATS & Recruitment Software, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 100Hires - AI ATS & Recruitment Software environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | number | Yes | Candidate ID (integer) or alias (string). |
city | string | — | Candidate city for location/timezone resolution. |
email | string | — | Candidate email address. |
phone | string | — | Candidate phone number. |
state | string | — | Candidate state or region. |
job_id | number | — | Job ID to create a new application for this candidate. |
country | string | — | Candidate country name or ISO code. |
profile | object | — | Key-value map of profile field answers. Keys can be question text or question_id. |
stage_id | number | — | Pipeline stage ID for the application. Requires job_id. |
timezone | string | — | IANA timezone (e.g. 'America/Los_Angeles'). Auto-resolved from city/country if omitted. |
last_name | string | — | Candidate last name. |
first_name | string | — | Candidate first name. |
Parameters from the server's own tool schema.
Why hires_update_candidate is rated Medium
The tool creates or modifies candidate data in the ATS system. The word 'Update' combined with the ability to change profile fields and resume information indicates a Write operation. It is reversible (data can be corrected or reverted), so it does not qualify as Destructive.
From the tool's definition Tool description explicitly states 'Update candidate fields, profile answers, and optional resume text' — this modifies existing candidate records reversibly.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs hires_update_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_update_candidate, this is the rule to start with:
hires_update_candidate 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.
The button opens the PolicyLayer dashboard: create your workspace, connect 100Hires - AI ATS & Recruitment Software, apply this rule, and every hires_update_candidate call is checked against it from then on.
Questions about hires_update_candidate
Update candidate fields, profile answers, and optional resume text. Used for bi-directional sync from ATS, CRM, sourcing, or enrichment tools. When the user provides an attached resume, parse it yourself from chat context and pass via resume_text — do not inline binary data. It is categorised as a Write tool in the 100Hires - AI ATS & Recruitment Software MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
hires_update_candidate accepts 12 parameters: id, city, email, phone, state, job_id, country, profile, stage_id, timezone, last_name, first_name. 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_update_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_update_candidate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the hires_update_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_update_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_update_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.
Across the catalogue