update_chat_message_attachment
Update description and/or pinned state for a file attached directly to a Huly channel message, direct-message message, or thread reply. The attachmentId must belong to the resolved target.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/update-chat-message-attachment.md
What update_chat_message_attachment does on Huly
AI agents use update_chat_message_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 update_chat_message_attachment is rated Medium
This tool modifies metadata properties of an existing attachment in a messaging system. It is reversible (description can be changed again, pinned state can be toggled) and has localized scope (affects only the specific attachment and its metadata).
From the tool's definition Tool description states it 'Update[s] description and/or pinned state for a file attached directly to a Huly channel message'. The verb 'update' combined with modifying metadata (description, pinned state) indicates reversible modification of existing data.
Attacks that exploit this kind of access
The rule that runs update_chat_message_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 update_chat_message_attachment, this is the rule to start with:
update_chat_message_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 update_chat_message_attachment call is checked against it from then on.
Questions about update_chat_message_attachment
Update description and/or pinned state for a file attached directly to a Huly channel message, direct-message message, or thread reply. The attachmentId must belong to the resolved target. 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 update_chat_message_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.
update_chat_message_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 update_chat_message_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 update_chat_message_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.
update_chat_message_attachment 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