update_recruiting_applicant
Update applicant status, assignee, startDate, and/or dueDate. applicant accepts raw _id, APP-<number>, or number; vacancy/candidate only disambiguate. Pass null to clear assignee, startDate, or dueDate.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/update-recruiting-applicant.md
What update_recruiting_applicant does on Huly
AI agents use update_recruiting_applicant 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 update_recruiting_applicant is rated Medium
This is a Write operation because it updates fields on an existing recruiting applicant object. The changes are reversible (fields can be updated again or reset via null), and no data is permanently deleted or destroyed. The severity is medium because misuse could affect recruitment workflows and applicant tracking, with moderate business impact but no irreversible loss or financial transaction involved.
From the tool's definition Tool description explicitly states 'Update applicant status, assignee, startDate, and/or dueDate' – this modifies existing data (recruiting applicant records) in a reversible manner.
Attacks that exploit this kind of access
The rule that runs update_recruiting_applicant 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 update_recruiting_applicant, this is the rule to start with:
update_recruiting_applicant 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 update_recruiting_applicant call is checked against it from then on.
Questions about update_recruiting_applicant
Update applicant status, assignee, startDate, and/or dueDate. applicant accepts raw _id, APP-<number>, or number; vacancy/candidate only disambiguate. Pass null to clear assignee, startDate, or dueDate. 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 update_recruiting_applicant: 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.
update_recruiting_applicant 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 update_recruiting_applicant 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 update_recruiting_applicant. 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.
update_recruiting_applicant 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