hires_list_candidates
List candidates filtered by job, stage, email, name, LinkedIn or dates. Prefer size <= 10.
This record as markdown: /tools/com-100hires-100hires/hires-list-candidates.md
What hires_list_candidates does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_list_candidates 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 |
|---|---|---|---|
q | string | — | Partial match on name or email |
page | number | — | |
size | number | — | |
view | string | — | summary omits the profile answers array |
email | string | — | Exact match |
job_id | number | — | |
include | string | — | Embed: applications (job titles and stages) |
linkedin | string | — | LinkedIn profile URL or alias |
stage_id | number | — | Pipeline stage id; combine with job_id |
full_name | string | — | |
company_id | number | — | |
created_after | number | string | — | Unix seconds or ISO-8601 |
Parameters from the server's own tool schema.
Why hires_list_candidates is rated Low
Even though hires_list_candidates only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs hires_list_candidates 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_candidates, this is the rule to start with:
hires_list_candidates 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_candidates call is checked against it from then on.
Questions about hires_list_candidates
List candidates filtered by job, stage, email, name, LinkedIn or dates. Prefer size <= 10. 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_candidates accepts 12 parameters: q, page, size, view, email, job_id, include, linkedin, stage_id, full_name, company_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_candidates: 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_candidates 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_candidates 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_candidates. 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_candidates 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