remove_issue_relation

Remove a relation between two issues. Mirrors add_issue_relation:

SERVERHuly SOURCEdugynoo/huly-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dugynoo-huly-mcp/remove-issue-relation.md

WHAT IT DOES

What remove_issue_relation does on Huly

AI agents call remove_issue_relation 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.

RISK

Why remove_issue_relation is rated Critical

Removing a relation between issues is a destructive operation that deletes an existing link. While it doesn't delete the issues themselves, the relation removal is not easily reversible and mirrors the add_issue_relation tool in reverse, making it a destructive action. Severity is medium since only a metadata relationship is lost, not core data.

From the tool's definition 'Remove a relation between two issues' - the tool removes/deletes an existing relationship between issues, which is an irreversible deletion action

Attacks that exploit this kind of access

RECOMMENDED RULE

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

remove_issue_relation Hidden

remove_issue_relation is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_issue_relation"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about remove_issue_relation

What does the remove_issue_relation tool do? +

Remove a relation between two issues. Mirrors add_issue_relation:. 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.

How do I enforce a policy on remove_issue_relation? +

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

remove_issue_relation is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit remove_issue_relation? +

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

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

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

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 218 Huly tools → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →delete_issue on Linear Kanban Server →remove_concept on MegaMemory → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →