hires_list_applications
List applications across all accessible jobs. Supports filtering by candidate, job, stage, status, AI score range, and date ranges. Use for pipeline analytics, sync jobs, and ATS dashboards. Avoid include=candidate or include=cv.text on large pages (each embeds heavy nested data); if the response...
This record as markdown: /tools/com-100hires-100hires/hires-list-applications.md
What hires_list_applications does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_list_applications to retrieve information from 100Hires - AI ATS & Recruitment Software without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | Page number (default 1). |
size | number | — | Items per page (default 25, max 100). |
sort | string | — | Sort order. Prefix with - for descending. Default: -created_at. |
job_id | number | — | Filter applications by job ID. |
status | string | — | Filter by application status: pending (active), hired, or rejected. |
include | string | — | Comma-separated relations to embed: `candidate`, `cv.text`. **Recommended: `candidate`** for pipeline / kanban / UI rendering — without it the widget shows cand |
stage_id | number | — | Filter applications by pipeline stage ID. Best used together with job_id. |
company_id | number | — | Filter by company ID. Omit for all accessible companies. |
ai_score_max | number | — | Return only applications with ai_score <= this value. |
ai_score_min | number | — | Return only applications with ai_score >= this value. |
candidate_id | number | — | Filter applications by candidate ID. |
created_after | number | string | — | Return only applications created at or after this time. Unix timestamp (seconds) or ISO-8601 string (e.g. 2026-05-11T00:00:00Z). Fractional seconds accepted but |
Parameters from the server's own tool schema.
Why hires_list_applications is rated Low
This tool queries and retrieves application data from the ATS system. It supports filtering and returns structured data for viewing pipelines and analytics. There is no creation, modification, deletion, or execution of external operations—it is purely a read operation. The mention of avoiding certain includes due to response size confirms it is a retrieval-only function.
From the tool's definition Tool name is "hires_list_applications" and description states "List applications across all accessible jobs. Supports filtering by candidate, job, stage, status, AI score range, and date ranges.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs hires_list_applications 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_list_applications, this is the rule to start with:
hires_list_applications is read-only, so it stays allowed. 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_list_applications call is checked against it from then on.
Questions about hires_list_applications
List applications across all accessible jobs. Supports filtering by candidate, job, stage, status, AI score range, and date ranges. Use for pipeline analytics, sync jobs, and ATS dashboards. Avoid include=candidate or include=cv.text on large pages (each embeds heavy nested data); if the response exceeds the budget the tool returns isError:true with error_code=response_too_large and retry hints. Each application embeds its current stage (IdName) directly in the response — this is sufficient for rendering kanban/pipeline views; you DO NOT need to call hires_get_job to fetch workflow_stages separately when rendering a pipeline. It is categorised as a Read tool in the 100Hires - AI ATS & Recruitment Software MCP Server, which means it retrieves data without modifying state.
hires_list_applications accepts 12 parameters: page, size, sort, job_id, status, include, stage_id, company_id, ai_score_max, ai_score_min, candidate_id, created_after. 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_list_applications: 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_list_applications is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hires_list_applications 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_list_applications. 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_list_applications 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