list_chat_message_attachments
List files attached directly to a Huly chat message target. target.kind supports channel_message, dm_message, and thread_reply; the tool resolves channel names and one-to-one DM participant display names for you.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-chat-message-attachments.md
What list_chat_message_attachments does on Huly
AI agents call list_chat_message_attachments 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_chat_message_attachments is rated Low
This tool retrieves and queries attachment metadata from chat messages without modifying, creating, or deleting any data. The verb 'list' and the lack of any side-effect language (create, update, delete) confirm it is a Read operation. Severity is low because listing attachments in chat has minimal blast radius—it only exposes already-shared file metadata to which the user likely has access.
From the tool's definition Tool description explicitly states 'List files attached' and 'resolves channel names', using list/read semantics with no modification, creation, or deletion language.
Attacks that exploit this kind of access
The rule that runs list_chat_message_attachments 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_chat_message_attachments, this is the rule to start with:
list_chat_message_attachments 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_chat_message_attachments call is checked against it from then on.
Questions about list_chat_message_attachments
List files attached directly to a Huly chat message target. target.kind supports channel_message, dm_message, and thread_reply; the tool resolves channel names and one-to-one DM participant display names for you. 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_chat_message_attachments: 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_chat_message_attachments 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_chat_message_attachments 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_chat_message_attachments. 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_chat_message_attachments 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