New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_recruiting_related_issue

Idempotently remove a Huly Related Issues entry (

SERVERHuly SOURCE@firfi/huly-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/remove-recruiting-related-issue.md

What remove_recruiting_related_issue does on Huly

AI agents call remove_recruiting_related_issue 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 remove_recruiting_related_issue is rated Critical

The tool performs an irreversible deletion operation on data (removing a related issues entry). This cannot be undone without manual intervention, making it Destructive rather than Write. The high severity reflects that an agent could remove important project relationships or issue linkages, impacting workflow visibility and traceability.

From the tool's definition Tool name contains 'remove' and description states 'remove a Huly Related Issues entry' — this irreversibly deletes a relationship/entry from the system. The idempotent qualifier indicates it won't error on re-execution, but the underlying action is deletion.

Questions about remove_recruiting_related_issue

What does the remove_recruiting_related_issue tool do? +

Idempotently remove a Huly Related Issues entry (. 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.

How do I enforce a policy on remove_recruiting_related_issue? +

Register the Huly MCP server in PolicyLayer and add a rule for remove_recruiting_related_issue: 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.

What risk level is remove_recruiting_related_issue? +

remove_recruiting_related_issue is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_recruiting_related_issue? +

Yes. Add a rate_limit block to the remove_recruiting_related_issue 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.

How do I block remove_recruiting_related_issue completely? +

Set action: deny in the PolicyLayer policy for remove_recruiting_related_issue. 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.

What MCP server provides remove_recruiting_related_issue? +

remove_recruiting_related_issue 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Huly's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.