link_document_to_issue
Link a Huly document to an issue. The link appears in the issue
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/link-document-to-issue.md
What link_document_to_issue does on Huly
AI agents use link_document_to_issue 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 link_document_to_issue is rated Medium
Linking a document to an issue is a reversible write operation that creates or modifies data (establishing a document-issue relationship). It does not execute arbitrary code, delete data, or involve financial transactions. The severity is medium because improper linking could clutter or misdirect issue tracking, but the operation is easily reversible and has limited blast radius.
From the tool's definition Tool description states 'Link a Huly document to an issue. The link appears in the issue' — this creates a new association/relationship between entities and modifies the issue's state by adding a link.
Attacks that exploit this kind of access
The rule that runs link_document_to_issue 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 link_document_to_issue, this is the rule to start with:
link_document_to_issue 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 link_document_to_issue call is checked against it from then on.
Questions about link_document_to_issue
Link a Huly document to an issue. The link appears in the issue. 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 link_document_to_issue: 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.
link_document_to_issue 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 link_document_to_issue 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 link_document_to_issue. 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.
link_document_to_issue is provided by the Huly MCP server (@firfi/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