delete_board_card
Permanently delete an already archived board card using Huly removeCollection. Active cards are rejected; call archive_board_card first.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-board-card.md
What delete_board_card does on Huly
AI agents call delete_board_card 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_board_card is rated Critical
This tool permanently deletes data (a board card) and cannot be undone. Even though it requires the card to be archived first, the deletion operation itself is irreversible, making it Destructive rather than Write. The high severity reflects the risk that an AI agent could permanently remove important project management data without recovery options.
From the tool's definition Tool description explicitly states "Permanently delete an already archived board card" and "removeCollection". The word "Permanently" combined with "delete" clearly indicates irreversible data removal.
Attacks that exploit this kind of access
The rule that runs delete_board_card 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_board_card, this is the rule to start with:
delete_board_card 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_board_card call is checked against it from then on.
Questions about delete_board_card
Permanently delete an already archived board card using Huly removeCollection. Active cards are rejected; call archive_board_card first. 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_board_card: 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_board_card 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_board_card 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_board_card. 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_board_card 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