list_recruiting_candidates
List persons that already have the Recruiting Candidate mixin. Use set_recruiting_candidate_profile, add_recruiting_candidate_skill, or create_recruiting_applicant to recruit-enable an existing person.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-recruiting-candidates.md
What list_recruiting_candidates does on Huly
AI agents call list_recruiting_candidates to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_recruiting_candidates is rated Low
This tool queries and retrieves a filtered list of candidates from the Huly recruiting system. It has no side effects, creates no new data, and modifies nothing. The description explicitly clarifies that modifications require separate tools (set_recruiting_candidate_profile, add_recruiting_candidate_skill, create_recruiting_applicant).
From the tool's definition Tool name contains 'list' and description states 'List persons that already have the Recruiting Candidate mixin', indicating a retrieval/query operation with no data modification.
Attacks that exploit this kind of access
The rule that runs list_recruiting_candidates safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_recruiting_candidates, this is the rule to start with:
list_recruiting_candidates 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 Huly, apply this rule, and every list_recruiting_candidates call is checked against it from then on.
Questions about list_recruiting_candidates
List persons that already have the Recruiting Candidate mixin. Use set_recruiting_candidate_profile, add_recruiting_candidate_skill, or create_recruiting_applicant to recruit-enable an existing person. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for list_recruiting_candidates: 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 Huly. Nothing to install.
list_recruiting_candidates 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 list_recruiting_candidates 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 list_recruiting_candidates. 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.
list_recruiting_candidates is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue