delete_recruiting_comment
Delete one comment attached directly to a Recruiting vacancy, candidate, applicant, review, or opinion. The commentId must belong to the resolved target.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-recruiting-comment.md
What delete_recruiting_comment does on Huly
AI agents call delete_recruiting_comment 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_comment is rated Critical
This tool permanently removes data (a recruiting comment) from the system with no undo mechanism. Destructive actions take precedence over Write actions. The severity is high because misuse could result in loss of important recruiting communications, feedback, or audit trails, though the blast radius is somewhat contained to a single comment rather than bulk deletion.
From the tool's definition Tool name contains 'delete' and description explicitly states 'Delete one comment'. The action is irreversible—once deleted, the comment cannot be recovered.
Attacks that exploit this kind of access
The rule that runs delete_recruiting_comment 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_comment, this is the rule to start with:
delete_recruiting_comment 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_comment call is checked against it from then on.
Questions about delete_recruiting_comment
Delete one comment attached directly to a Recruiting vacancy, candidate, applicant, review, or opinion. The commentId must belong to the resolved target. 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_comment: 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_comment 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_comment 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_comment. 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_comment 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