add_recruiting_candidate_skill
Attach a skill to a candidate. candidate accepts person _id, email, or exact name. skill accepts title or tag ID; missing skill titles are created. Optional category/color apply only to newly created skill tags.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/add-recruiting-candidate-skill.md
What add_recruiting_candidate_skill does on Huly
AI agents use add_recruiting_candidate_skill to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why add_recruiting_candidate_skill is rated Medium
This tool creates or modifies data reversibly: it attaches skills to candidate records and creates new skill tags if they don't exist. These are write operations that can be undone (skills can be removed, tags deleted). It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states 'Attach a skill to a candidate' and 'missing skill titles are created', indicating data creation and modification operations. The tool modifies candidate records by adding skills and can create new skill tags with optional metadata.
Attacks that exploit this kind of access
The rule that runs add_recruiting_candidate_skill 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 add_recruiting_candidate_skill, this is the rule to start with:
add_recruiting_candidate_skill 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 Huly, apply this rule, and every add_recruiting_candidate_skill call is checked against it from then on.
Questions about add_recruiting_candidate_skill
Attach a skill to a candidate. candidate accepts person _id, email, or exact name. skill accepts title or tag ID; missing skill titles are created. Optional category/color apply only to newly created skill tags. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly MCP server in PolicyLayer and add a rule for add_recruiting_candidate_skill: 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.
add_recruiting_candidate_skill 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 add_recruiting_candidate_skill 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 add_recruiting_candidate_skill. 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.
add_recruiting_candidate_skill 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