hires_move_application
Moves an application to a specific pipeline stage for explicit stage transitions in workflow orchestration. Requires the target stage_id (available via the job's pipeline_stages).
This record as markdown: /tools/com-100hires-100hires/hires-move-application.md
What hires_move_application does on 100Hires - AI ATS & Recruitment Software
AI agents use hires_move_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 |
|---|---|---|---|
id | number | Yes | Application ID. |
include | string | — | Comma-separated relations to embed: candidate, cv.text, job. |
stage_id | number | Yes | Target pipeline stage ID. |
Parameters from the server's own tool schema.
Why hires_move_application is rated Medium
This tool modifies application metadata (pipeline stage assignment) reversibly within a recruitment workflow. It does not delete data (not Destructive), execute arbitrary code (not Execute), move money (not Financial), or merely read data (not Read).
From the tool's definition Tool name 'hires_move_application' and description 'Moves an application to a specific pipeline stage' indicates modification of application state/workflow status. The word 'Moves' reflects a state change operation.
Attacks that exploit this kind of access
The rule that runs hires_move_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_move_application, this is the rule to start with:
hires_move_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_move_application call is checked against it from then on.
Questions about hires_move_application
Moves an application to a specific pipeline stage for explicit stage transitions in workflow orchestration. Requires the target stage_id (available via the job's pipeline_stages). 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_move_application accepts 3 parameters: id, include, stage_id. Required: id, stage_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_move_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_move_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_move_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_move_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_move_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