update_issue_template

Update fields on an existing Huly issue template. Only provided fields are modified.

SERVERHuly SOURCEdugynoo/huly-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about update_issue_template

What does the update_issue_template tool do? +

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.

How do I enforce a policy on update_issue_template? +

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.

What risk level is update_issue_template? +

update_issue_template is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_issue_template? +

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.

How do I block update_issue_template completely? +

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.

What MCP server provides update_issue_template? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Huly's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.