# remove_recruiting_related_issue

Idempotently remove a Huly Related Issues entry (

Agent View of the PolicyLayer registry record for `remove_recruiting_related_issue`. HTML page: https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/remove-recruiting-related-issue

## Facts

- Tool: `remove_recruiting_related_issue`
- Server: Huly (`@firfi/huly-mcp`) — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp.md
- Install: `npx -y @firfi/huly-mcp`
- Homepage: https://github.com/dearlordylord/huly-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "remove_recruiting_related_issue",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Huly:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_recruiting_related_issue"
  ]
}
```

## Other tools on Huly (517)

- `cancel_approval_request` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/cancel-approval-request.md
- `cancel_execution` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/cancel-execution.md
- `delete_activity_reply` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-activity-reply.md
- `delete_association` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-association.md
- `delete_attachment` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-attachment.md
- `delete_board_card` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-board-card.md
- `delete_board_label` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-board-label.md
- `delete_card` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-card.md
- `delete_card_comment` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-card-comment.md
- `delete_channel` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-channel.md
- `delete_channel_message` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-channel-message.md
- `delete_chat_message_attachment` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-chat-message-attachment.md
- `delete_class_collaborator_metadata` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-class-collaborator-metadata.md
- `delete_comment` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-comment.md
- `delete_component` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-component.md
- `delete_dm_message` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-dm-message.md
- `delete_document` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-document.md
- `delete_drawing` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-drawing.md
- `delete_drive` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-drive.md
- `delete_drive_file_comment` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-drive-file-comment.md
- `delete_drive_item` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-drive-item.md
- `delete_event` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-event.md
- `delete_huly_attribute` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-huly-attribute.md
- `delete_huly_enum` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-huly-enum.md
- `delete_huly_permission` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-huly-permission.md
- `delete_huly_sequence` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-huly-sequence.md
- `delete_inventory_category` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-inventory-category.md
- `delete_inventory_product` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-inventory-product.md
- `delete_inventory_product_attachment` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-inventory-product-attachment.md
- `delete_inventory_product_comment` — Destructive — https://policylayer.com/tools/io-github-dearlordylord-huly-mcp/delete-inventory-product-comment.md
- …and 487 more: https://policylayer.com/tools/io-github-dearlordylord-huly-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-dearlordylord-huly-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-dearlordylord-huly-mcp