remove_template_child
Remove a child (sub-task) template from an issue template by its child ID. Get child IDs from get_issue_template response.
This record as markdown: /tools/dugynoo-huly-mcp/remove-template-child.md
What remove_template_child does on Huly
AI agents call remove_template_child 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 remove_template_child is rated Critical
This tool permanently removes a child task template from a parent issue template. This is an irreversible operation that cannot be undone without re-adding the relationship. Although it doesn't delete the child template itself, it destructively removes the hierarchical relationship, which could break project template structures that depend on this composition.
From the tool's definition Tool name 'remove_template_child' and description states it 'Remove[s] a child (sub-task) template' — the verb 'remove' in the context of deleting template relationships indicates irreversible deletion of data structure associations.
Attacks that exploit this kind of access
The rule that runs remove_template_child 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_template_child, this is the rule to start with:
remove_template_child 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 remove_template_child call is checked against it from then on.
Questions about remove_template_child
Remove a child (sub-task) template from an issue template by its child ID. Get child IDs from get_issue_template response. 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 remove_template_child: 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.
remove_template_child 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 remove_template_child 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 remove_template_child. 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.
remove_template_child 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.
Across the catalogue