update_issue_template
Update fields on an existing Huly issue template. Only provided fields are modified.
This record as markdown: /tools/dugynoo-huly-mcp/update-issue-template.md
What update_issue_template does on Huly
AI agents use update_issue_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 update_issue_template is rated Medium
This tool creates or modifies data in a reversible manner (classic Write operation). It updates an existing template, not executing code or deleting data. The severity is medium because template modifications could affect multiple issues if the template is widely used, but changes are reversible and typically auditable in project management systems.
From the tool's definition Tool description states 'Update fields on an existing Huly issue template' — this modifies data reversibly. The 'Only provided fields are modified' phrasing indicates selective updates rather than wholesale deletion or destructive operations.
Attacks that exploit this kind of access
The rule that runs update_issue_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 update_issue_template, this is the rule to start with:
update_issue_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 update_issue_template call is checked against it from then on.
Questions about update_issue_template
Update fields on an existing Huly issue template. Only provided fields are modified. 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 update_issue_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.
update_issue_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 update_issue_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 update_issue_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.
update_issue_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