set_related_issue_target
Set the default destination project for related issues from a space or object class. For space, creates or updates a spaceRule. For objectClass, only updates an existing classRule; this tool never creates classRule targets. Pass targetProject as a project identifier, or null to clear the default ...
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/set-related-issue-target.md
What set_related_issue_target does on Huly
AI agents use set_related_issue_target 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_related_issue_target is rated Medium
This tool creates or updates configuration rules (spaceRule/classRule) that control routing behavior for related issues. While reversible (can be updated or cleared with null), it modifies system-level settings that affect workflow behavior and could impact multiple users' issue destinations if misconfigured.
From the tool's definition Tool description explicitly states 'creates or updates a spaceRule' and 'updates an existing classRule', indicating it modifies configuration data in the system.
Attacks that exploit this kind of access
The rule that runs set_related_issue_target 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_related_issue_target, this is the rule to start with:
set_related_issue_target 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_related_issue_target call is checked against it from then on.
Questions about set_related_issue_target
Set the default destination project for related issues from a space or object class. For space, creates or updates a spaceRule. For objectClass, only updates an existing classRule; this tool never creates classRule targets. Pass targetProject as a project identifier, or null to clear the default destination project. 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_related_issue_target: 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_related_issue_target 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_related_issue_target 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_related_issue_target. 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_related_issue_target 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