hires_list_candidate_tags
List all tags assigned to a candidate. Useful for segmentation and audience-based automations.
This record as markdown: /tools/com-100hires-100hires/hires-list-candidate-tags.md
What hires_list_candidate_tags does on 100Hires - AI ATS & Recruitment Software
AI agents call hires_list_candidate_tags 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 |
|---|---|---|---|
id | string | number | Yes | Candidate ID (integer) or alias (string). |
Parameters from the server's own tool schema.
Why hires_list_candidate_tags is rated Low
The tool retrieves and displays existing tag data for a candidate without creating, modifying, or deleting any information. It is purely informational, supporting segmentation and automation visibility without changing state. Low severity due to minimal blast radius—an AI agent misusing this would only retrieve tag metadata already associated with the candidate.
From the tool's definition Tool name contains 'list' and description states 'List all tags assigned to a candidate.' This is a read-only query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs hires_list_candidate_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_list_candidate_tags, this is the rule to start with:
hires_list_candidate_tags 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_candidate_tags call is checked against it from then on.
Questions about hires_list_candidate_tags
List all tags assigned to a candidate. Useful for segmentation and audience-based automations. 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_candidate_tags accepts 1 parameter: id. Required: 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_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 - AI ATS & Recruitment Software. Nothing to install.
hires_list_candidate_tags 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_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_list_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_list_candidate_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