delete_recruiting_applicant
Delete an applicant with Huly removeCollection. applicant accepts raw _id, APP-<number>, or number; vacancy/candidate can disambiguate APP numbers.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-recruiting-applicant.md
What delete_recruiting_applicant does on Huly
AI agents call delete_recruiting_applicant to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_recruiting_applicant is rated Critical
This tool performs irreversible deletion of applicant data from Huly. The use of 'removeCollection' and the explicit 'Delete' verb indicates data is permanently removed and cannot be undone. This is a destructive action with significant blast radius if triggered unintentionally—losing recruiting applicant records could impact hiring processes.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete an applicant' with 'removeCollection', which irreversibly removes a recruiting applicant record.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_recruiting_applicant, this is the rule to start with:
delete_recruiting_applicant is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every delete_recruiting_applicant call is checked against it from then on.
Questions about delete_recruiting_applicant
Delete an applicant with Huly removeCollection. applicant accepts raw _id, APP-<number>, or number; vacancy/candidate can disambiguate APP numbers. It is categorised as a Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Huly MCP server in PolicyLayer and add a rule for delete_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.
delete_recruiting_applicant is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue