list_comments
List comments on a Huly issue. Returns comments sorted by creation date (oldest first).
This record as markdown: /tools/dugynoo-huly-mcp/list-comments.md
What list_comments does on Huly
AI agents call list_comments to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_comments is rated Low
This tool retrieves and queries existing comments without creating, modifying, deleting, or executing any operations. It has minimal blast radius if misused by an AI agent, as it only exposes read access to comment data that the authenticated user already has permission to view.
From the tool's definition Tool name is 'list_comments' and description states it 'List comments on a Huly issue' and 'Returns comments sorted by creation date' — purely a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs list_comments 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 list_comments, this is the rule to start with:
list_comments is read-only, so it stays allowed. 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 list_comments call is checked against it from then on.
Questions about list_comments
List comments on a Huly issue. Returns comments sorted by creation date (oldest first). It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for list_comments: 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.
list_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_comments 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 list_comments. 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.
list_comments 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