archive_board
Archive a Huly board by board _id or exact board name. This hides the board but does not delete cards.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/archive-board.md
What archive_board does on Huly
AI agents use archive_board to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why archive_board is rated Medium
Archiving is a state modification operation that can typically be undone by unarchiving. While it removes visibility of the board, it does not irreversibly delete data or cards. This places it in the Write category (modifies data reversibly) rather than Destructive. Severity is medium because archiving a board affects visibility and access for team members, but the operation is reversible and no data is destroyed.
From the tool's definition Tool description states 'Archive a Huly board' and 'This hides the board but does not delete cards.' The action modifies the board state (archiving) but is explicitly reversible ('does not delete').
Attacks that exploit this kind of access
The rule that runs archive_board 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 archive_board, this is the rule to start with:
archive_board stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every archive_board call is checked against it from then on.
Questions about archive_board
Archive a Huly board by board _id or exact board name. This hides the board but does not delete cards. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly MCP server in PolicyLayer and add a rule for archive_board: 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.
archive_board is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the archive_board 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 archive_board. 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.
archive_board 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.
This server
Across the catalogue