hires_update_application
Update application fields. stage_id performs a full stage transition with the target stage's automation, like hires_move_application.
This record as markdown: /tools/com-100hires-100hires/hires-update-application.md
What hires_update_application does on 100Hires - AI ATS & Recruitment Software
AI agents use hires_update_application 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 |
|---|---|---|---|
cv | object | — | Replace or attach a CV |
id | number | Yes | |
include | string | — | Embed: candidate, cv.text, job |
stage_id | number | — | Target stage; runs its workflow automation |
is_disqualified | boolean | — |
Parameters from the server's own tool schema.
Why hires_update_application is rated Medium
An AI agent can call hires_update_application faster than any human can review: one bad instruction and it creates or modifies resources in 100Hires - AI ATS & Recruitment Software by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs hires_update_application 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_application, this is the rule to start with:
hires_update_application 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_application call is checked against it from then on.
Questions about hires_update_application
Update application fields. stage_id performs a full stage transition with the target stage's automation, like hires_move_application. 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_application accepts 5 parameters: cv, id, include, stage_id, is_disqualified. 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_application: 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_application 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_application 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_application. 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_application 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