set_issue_milestone
Set or clear the milestone on a Huly issue. Pass null for milestone to clear it.
This record as markdown: /tools/dugynoo-huly-mcp/set-issue-milestone.md
What set_issue_milestone does on Huly
AI agents use set_issue_milestone 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 set_issue_milestone is rated Medium
This tool creates or modifies data (issue milestone assignment) without irreversibly deleting anything. The milestone can be changed or cleared, making it a reversible Write operation rather than Destructive. Severity is medium because incorrect milestone assignments could disrupt project planning and workflows, but the change is easily correctable.
From the tool's definition 'Set or clear the milestone on a Huly issue' — modifies issue metadata (milestone field) reversibly. Passing null clears it, indicating the operation is not destructive but rather a state update.
Attacks that exploit this kind of access
The rule that runs set_issue_milestone 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 set_issue_milestone, this is the rule to start with:
set_issue_milestone 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 set_issue_milestone call is checked against it from then on.
Questions about set_issue_milestone
Set or clear the milestone on a Huly issue. Pass null for milestone to clear it. 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 set_issue_milestone: 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.
set_issue_milestone 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 set_issue_milestone 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 set_issue_milestone. 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.
set_issue_milestone 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