delete_related_issue_space_target
Delete the spaceRule that chooses the default destination project for related issues from one space. This only deletes spaceRule targets; classRule deletion is intentionally unsupported because class rules may be model-provided.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-related-issue-space-target.md
What delete_related_issue_space_target does on Huly
AI agents call delete_related_issue_space_target to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_related_issue_space_target is rated Critical
This tool irreversibly deletes configuration data (spaceRule targets) that affects system behavior. While not a direct deletion of user content, it removes rules that cannot be easily recovered and impacts the default routing of related issues across the system. This meets the Destructive category as it performs an action that cannot be undone and affects application configuration.
From the tool's definition The tool description explicitly states "Delete the spaceRule" and "deletes spaceRule targets". The verb "delete" combined with the irreversible nature of removing configuration rules that govern default project destinations makes this a destructive operation.
Attacks that exploit this kind of access
The rule that runs delete_related_issue_space_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 delete_related_issue_space_target, this is the rule to start with:
delete_related_issue_space_target is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every delete_related_issue_space_target call is checked against it from then on.
Questions about delete_related_issue_space_target
Delete the spaceRule that chooses the default destination project for related issues from one space. This only deletes spaceRule targets; classRule deletion is intentionally unsupported because class rules may be model-provided. It is categorised as a Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Huly MCP server in PolicyLayer and add a rule for delete_related_issue_space_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.
delete_related_issue_space_target is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_related_issue_space_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 delete_related_issue_space_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.
delete_related_issue_space_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.
Across the catalogue