add_issue_attachment
Add an attachment to a Huly issue. Convenience method that finds the issue by project and identifier. Provide ONE of: filePath, fileUrl, or data.
This record as markdown: /tools/dugynoo-huly-mcp/add-issue-attachment.md
What add_issue_attachment does on Huly
AI agents use add_issue_attachment 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 add_issue_attachment is rated Medium
This is a Write operation because it creates a new attachment and modifies an issue's data structure reversibly. While attachments can later be removed, the action itself is not destructive—it adds content rather than deleting or overwriting. Severity is medium because an agent could upload malicious files or spam attachments, but the blast radius is limited to a single issue and can be undone.
From the tool's definition 'Add an attachment to a Huly issue' — the tool creates and associates a new attachment resource with an issue, modifying the issue's state by adding a file reference (filePath, fileUrl, or data).
Attacks that exploit this kind of access
The rule that runs add_issue_attachment 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 add_issue_attachment, this is the rule to start with:
add_issue_attachment 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 add_issue_attachment call is checked against it from then on.
Questions about add_issue_attachment
Add an attachment to a Huly issue. Convenience method that finds the issue by project and identifier. Provide ONE of: filePath, fileUrl, or data. 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 add_issue_attachment: 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.
add_issue_attachment 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 add_issue_attachment 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 add_issue_attachment. 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.
add_issue_attachment 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