hires_add_candidate_tags
Add one or more tags to a candidate. Used for campaign tagging, qualification labels, and source attribution.
This record as markdown: /tools/100hires-mcp-server/hires-add-candidate-tags.md
What hires_add_candidate_tags does on 100Hires MCP Server
AI agents use hires_add_candidate_tags 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_add_candidate_tags is rated Medium
This tool modifies candidate records by adding tags (metadata), which is a reversible write operation. It does not delete data, execute code, move money, or trigger external side effects. However, it affects recruiting workflow and candidate visibility, so severity is medium rather than low. The confidence is high because the action is clearly stated as 'add tags' without ambiguity about side effects.
From the tool's definition Tool name 'hires_add_candidate_tags' and description states 'Add one or more tags to a candidate' — this creates or modifies candidate metadata in the ATS system.
Attacks that exploit this kind of access
The rule that runs hires_add_candidate_tags 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_add_candidate_tags, this is the rule to start with:
hires_add_candidate_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 MCP Server, apply this rule, and every hires_add_candidate_tags call is checked against it from then on.
Questions about hires_add_candidate_tags
Add one or more tags to a candidate. Used for campaign tagging, qualification labels, and source attribution. 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_add_candidate_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 MCP Server. Nothing to install.
hires_add_candidate_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_add_candidate_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_add_candidate_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_add_candidate_tags 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