hires_list_origins
List candidate origin taxonomy values. Use for attribution analytics and source normalization.
This record as markdown: /tools/com-100hires-100hires/hires-list-origins.md
What hires_list_origins does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_list_origins 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.
Why hires_list_origins is rated Low
This tool retrieves reference data (origin taxonomy values) for analytical purposes. It has no side effects, cannot modify data, and presents minimal risk of misuse. The low severity reflects that exposure of recruitment origin taxonomy is informational and non-sensitive compared to other HR operations like candidate deletion or mass rejection on this server.
From the tool's definition Tool name contains 'list' and description states 'List candidate origin taxonomy values' — a retrieval operation with no modification. Described use cases are 'attribution analytics and source normalization,' which are read-only analytical purposes.
Attacks that exploit this kind of access
The rule that runs hires_list_origins 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_origins, this is the rule to start with:
hires_list_origins 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_origins call is checked against it from then on.
Questions about hires_list_origins
List candidate origin taxonomy values. Use for attribution analytics and source normalization. It is categorised as a Read tool in the 100Hires - AI ATS & Recruitment Software MCP Server, which means it retrieves data without modifying state.
Register the 100Hires - AI ATS & Recruitment Software MCP server in PolicyLayer and add a rule for hires_list_origins: 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_origins 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_origins 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_origins. 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_origins 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