update_board_label
Update a board label definition by TagElement _id or exact title. At least one of title, color, description, or category is required.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/update-board-label.md
What update_board_label does on Huly
AI agents use update_board_label 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 update_board_label is rated Medium
This tool modifies existing label metadata (title, color, description, category) in a board system. It is reversible (can be updated again), so it qualifies as Write rather than Destructive. The blast radius is medium—misconfigured label changes could confuse team organization but would not cause permanent data loss or execute arbitrary code. No financial impact.
From the tool's definition Tool name 'update_board_label' and description 'Update a board label definition' explicitly performs a modification operation. The phrase 'At least one of title, color, description, or category is required' confirms the tool changes label properties.
Attacks that exploit this kind of access
The rule that runs update_board_label 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 update_board_label, this is the rule to start with:
update_board_label 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 update_board_label call is checked against it from then on.
Questions about update_board_label
Update a board label definition by TagElement _id or exact title. At least one of title, color, description, or category is required. 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 update_board_label: 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.
update_board_label 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 update_board_label 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 update_board_label. 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.
update_board_label 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