set_issue_component
Set or clear the component on a Huly issue. Pass null for component to clear it.
This record as markdown: /tools/dugynoo-huly-mcp/set-issue-component.md
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.
Why set_issue_component is rated Medium
This tool creates or modifies metadata (component field) on an existing issue in a reversible manner. It does not execute code, trigger external operations, delete data irreversibly, or move money. The blast radius is medium because incorrect component assignment could misdirect issue routing, workflow automation, or team assignments in a project management system, but the change is easily reversible.
From the tool's definition Tool name 'set_issue_component' and description 'Set or clear the component on a Huly issue' indicate modification of issue metadata. The ability to pass null to clear indicates reversible state changes.
Attacks that exploit this kind of access
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 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 set_issue_component call is checked against it from then on.
Questions about set_issue_component
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.
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.
set_issue_component 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 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.
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.
set_issue_component is provided by the Huly MCP server (dugynoo/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