hires_list_rejection_reasons
List configured rejection reasons for the company. Use to validate rejection actions and analytics.
This record as markdown: /tools/com-100hires-100hires/hires-list-rejection-reasons.md
What hires_list_rejection_reasons does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_list_rejection_reasons 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 |
|---|---|---|---|
company_id | number | — | Target company ID (uses default company when omitted) |
Parameters from the server's own tool schema.
Why hires_list_rejection_reasons is rated Low
This tool retrieves a static configuration (rejection reasons) from the ATS system. It has no side effects, does not modify data, does not execute code or commands, and does not delete or move data. It is purely informational, fitting the Read category. Severity is low as misuse would only expose HR configuration data relevant to understanding rejection policies, with minimal blast radius.
From the tool's definition Tool name contains 'list' and description states 'List configured rejection reasons' with use cases limited to 'validate rejection actions and analytics' — retrieves data without modification.
Attacks that exploit this kind of access
The rule that runs hires_list_rejection_reasons 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_rejection_reasons, this is the rule to start with:
hires_list_rejection_reasons 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_rejection_reasons call is checked against it from then on.
Questions about hires_list_rejection_reasons
List configured rejection reasons for the company. Use to validate rejection actions and analytics. 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_rejection_reasons accepts 1 parameter: company_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_list_rejection_reasons: 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_rejection_reasons 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_rejection_reasons 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_rejection_reasons. 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_rejection_reasons 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