hires_batch_reject_applications
Reject multiple applications in one request with an optional rejection reason. Returns per-item results with partial success support. Max 100 application IDs per request.
This record as markdown: /tools/100hires-mcp-server/hires-batch-reject-applications.md
What hires_batch_reject_applications does on 100Hires MCP Server
AI agents use hires_batch_reject_applications to create or update resources in 100Hires MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 100Hires MCP Server environment.
Why hires_batch_reject_applications is rated Medium
This tool changes application state from active/pending to rejected, which is a data modification. While rejections affect candidates (e.g., they see rejection notifications and lose consideration), the operation is reversible: most ATS systems allow restoring rejected applications or re-opening them.
From the tool's definition Tool name contains 'batch_reject_applications' and description states it 'Reject multiple applications in one request'.
Attacks that exploit this kind of access
The rule that runs hires_batch_reject_applications safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 100Hires MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hires_batch_reject_applications, this is the rule to start with:
hires_batch_reject_applications 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 MCP Server, apply this rule, and every hires_batch_reject_applications call is checked against it from then on.
Questions about hires_batch_reject_applications
Reject multiple applications in one request with an optional rejection reason. Returns per-item results with partial success support. Max 100 application IDs per request. It is categorised as a Write tool in the 100Hires MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the 100Hires MCP Server MCP server in PolicyLayer and add a rule for hires_batch_reject_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 MCP Server. Nothing to install.
hires_batch_reject_applications 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_batch_reject_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_batch_reject_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_batch_reject_applications is provided by the 100Hires MCP Server MCP server (100hires/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 100Hires MCP Server, and thousands of servers like it.
This server
Across the catalogue