get_recruiting_applicant_match
Get one read-only generated Recruiting applicant match by raw applicant-match _id. Returns candidate, complete state, generated vacancy text, summary, response markdown, and timestamps.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/get-recruiting-applicant-match.md
What get_recruiting_applicant_match does on Huly
AI agents call get_recruiting_applicant_match 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 get_recruiting_applicant_match is rated Low
This tool retrieves and queries data from the recruiting system without any side effects. The 'read-only' designation and the nature of returned fields (candidate info, state, text, summary, timestamps) confirm it is purely a data retrieval operation with no capability to modify system state or trigger external actions.
From the tool's definition Tool description explicitly states 'read-only' and uses 'Get' verb with retrieval semantics (fetch applicant match by ID, returns data). No modification, deletion, execution, or financial operations are performed.
Attacks that exploit this kind of access
The rule that runs get_recruiting_applicant_match 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 get_recruiting_applicant_match, this is the rule to start with:
get_recruiting_applicant_match 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 get_recruiting_applicant_match call is checked against it from then on.
Questions about get_recruiting_applicant_match
Get one read-only generated Recruiting applicant match by raw applicant-match _id. Returns candidate, complete state, generated vacancy text, summary, response markdown, and timestamps. 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 get_recruiting_applicant_match: 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.
get_recruiting_applicant_match 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 get_recruiting_applicant_match 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 get_recruiting_applicant_match. 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.
get_recruiting_applicant_match 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