set_issue_component

Set or clear the component on a Huly issue. Pass null for component to clear it.

SERVERHuly SOURCE@firfi/huly-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/set-issue-component.md

WHAT IT DOES

What set_issue_component does on Huly

AI agents use set_issue_component 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.

RISK

Why set_issue_component is rated Medium

This tool modifies issue data (component field) in a reversible manner without deleting underlying data or executing arbitrary code. It fits the Write category (creates or modifies data reversibly). Severity is medium because changing issue components could affect workflows, assignments, or tracking, but the change is reversible and doesn't destroy data or commit financial obligations.

From the tool's definition Tool description states 'Set or clear the component on a Huly issue', indicating modification of issue metadata. The ability to pass null to clear the component confirms reversible update capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs set_issue_component 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 set_issue_component, this is the rule to start with:

set_issue_component Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "set_issue_component": {
      "limits": [
        {
          "counter": "set_issue_component_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every set_issue_component call is checked against it from then on.

FAQ

Questions about set_issue_component

What does the set_issue_component tool do? +

Set or clear the component on a Huly issue. Pass null for component to clear it. 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.

How do I enforce a policy on set_issue_component? +

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

set_issue_component is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_issue_component? +

Yes. Add a rate_limit block to the set_issue_component 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 set_issue_component completely? +

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

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

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 518 Huly tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →