hires_batch_remove_tags
Remove tags from multiple candidates in one request (max 100). Returns per-item results with partial success support.
This record as markdown: /tools/com-100hires-100hires/hires-batch-remove-tags.md
What hires_batch_remove_tags does on 100Hires - AI ATS & Recruitment Software
AI agents use hires_batch_remove_tags to create or update resources in 100Hires - AI ATS & Recruitment Software, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 100Hires - AI ATS & Recruitment Software environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
ids | array | Yes | Candidate IDs to remove tags from (max 100). |
tags | array | Yes | Tag names to remove. |
Parameters from the server's own tool schema.
Why hires_batch_remove_tags is rated Medium
Removing tags modifies candidate records but is generally reversible (tags can be re-added), placing this in the Write category. The blast radius is medium since it affects up to 100 candidates at once, but tag removal is not irreversible data destruction.
From the tool's definition Remove tags from multiple candidates in one request
Attacks that exploit this kind of access
The rule that runs hires_batch_remove_tags 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_batch_remove_tags, this is the rule to start with:
hires_batch_remove_tags 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 - AI ATS & Recruitment Software, apply this rule, and every hires_batch_remove_tags call is checked against it from then on.
Questions about hires_batch_remove_tags
Remove tags from multiple candidates in one request (max 100). Returns per-item results with partial success support. It is categorised as a Write tool in the 100Hires - AI ATS & Recruitment Software MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
hires_batch_remove_tags accepts 2 parameters: ids, tags. Required: ids, tags. 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_batch_remove_tags: 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_batch_remove_tags 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_remove_tags 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_remove_tags. 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_remove_tags 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