save_attachment

Save/bookmark an attachment for later reference. Idempotent when already saved.

SERVERHuly SOURCE@firfi/huly-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dearlordylord-huly-mcp/save-attachment.md

WHAT IT DOES

What save_attachment does on Huly

AI agents use save_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.

RISK

Why save_attachment is rated Medium

This tool modifies state (bookmarking/saving) in a reversible manner typical of Write operations. It creates or updates a reference without irreversibly deleting, destroying, or executing external code. The idempotent nature and limited scope (bookmarking only) suggest low severity even if misused by an agent.

From the tool's definition Tool description states 'Save/bookmark an attachment for later reference' and is explicitly 'Idempotent when already saved', indicating a reversible state change without data loss or financial impact.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs save_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 save_attachment, this is the rule to start with:

save_attachment Rate-limited

save_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_attachment": {
      "limits": [
        {
          "counter": "save_attachment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every save_attachment call is checked against it from then on.

FAQ

Questions about save_attachment

What does the save_attachment tool do? +

Save/bookmark an attachment for later reference. Idempotent when already saved. 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.

How do I enforce a policy on save_attachment? +

Register the Huly MCP server in PolicyLayer and add a rule for save_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.

What risk level is save_attachment? +

save_attachment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit save_attachment? +

Yes. Add a rate_limit block to the save_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.

How do I block save_attachment completely? +

Set action: deny in the PolicyLayer policy for save_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.

What MCP server provides save_attachment? +

save_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.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 518 Huly tools →

Across the catalogue

save_snapshot on Why Did You Render → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →