update_attachment
Update attachment metadata (description, pinned status).
This record as markdown: /tools/dugynoo-huly-mcp/update-attachment.md
What update_attachment does on Huly
AI agents use update_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_attachment is rated Medium
This tool modifies metadata fields (description, pinned status) of attachments but does not delete or destroy data, nor does it execute arbitrary operations or commit financial transactions. Metadata updates are reversible and fall squarely into the Write category. The blast radius is minimal since changing descriptions or pin status has no cascading security or operational impact.
From the tool's definition Tool name 'update_attachment' and description stating it 'Update[s] attachment metadata (description, pinned status)' indicates modification of existing data fields in a reversible manner.
Attacks that exploit this kind of access
The rule that runs update_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_attachment, this is the rule to start with:
update_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_attachment call is checked against it from then on.
Questions about update_attachment
Update attachment metadata (description, pinned status). 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_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_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_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_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_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