create_issue_from_template
Create a new issue from a template. Applies template defaults, allowing overrides for specific fields. If the template has children (sub-task templates), sub-issues are created automatically unless includeChildren is set to false. Returns the created issue identifier and count of children created.
This record as markdown: /tools/dugynoo-huly-mcp/create-issue-from-template.md
What create_issue_from_template does on Huly
AI agents use create_issue_from_template 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 create_issue_from_template is rated Medium
This is a Write operation because it creates new data (issues and sub-issues) in a reversible manner. While issues can typically be deleted later, the primary effect is creation/insertion of records. It's not Read (queries only), not Execute (doesn't run arbitrary code), not Destructive (doesn't permanently erase), and not Financial.
From the tool's definition create_issue_from_template creates new issues in a project management system, with the description explicitly stating it 'Create a new issue from a template' and automatically creates sub-issues (children).
Attacks that exploit this kind of access
The rule that runs create_issue_from_template 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 create_issue_from_template, this is the rule to start with:
create_issue_from_template 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 create_issue_from_template call is checked against it from then on.
Questions about create_issue_from_template
Create a new issue from a template. Applies template defaults, allowing overrides for specific fields. If the template has children (sub-task templates), sub-issues are created automatically unless includeChildren is set to false. Returns the created issue identifier and count of children created. 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 create_issue_from_template: 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.
create_issue_from_template 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 create_issue_from_template 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 create_issue_from_template. 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.
create_issue_from_template 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