hires_hire_application
Mark an application as hired. This is the finalization step in a hiring workflow. The application status changes to 'hired' and hired_at is set.
This record as markdown: /tools/com-100hires-100hires/hires-hire-application.md
What hires_hire_application does on 100Hires - AI ATS & Recruitment Software
AI agents use hires_hire_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. |
Parameters from the server's own tool schema.
Why hires_hire_application is rated Medium
This tool modifies application records by setting their status to 'hired' and recording a timestamp. While it triggers a significant business action (finalizing a hire), it is reversible (status can be changed back, record can be edited). It does not delete data or commit financial transactions.
From the tool's definition Tool description states 'Mark an application as hired' and 'application status changes to hired and hired_at is set' — this creates/modifies data (application status and timestamp) in the ATS system.
Attacks that exploit this kind of access
The rule that runs hires_hire_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_hire_application, this is the rule to start with:
hires_hire_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_hire_application call is checked against it from then on.
Questions about hires_hire_application
Mark an application as hired. This is the finalization step in a hiring workflow. The application status changes to 'hired' and hired_at is set. 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_hire_application accepts 2 parameters: id, include. 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_hire_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_hire_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_hire_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_hire_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_hire_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