update_lead_attachment

Update description or pinned state for an attachment only when it belongs to one exact lead.

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/update-lead-attachment.md

WHAT IT DOES

What update_lead_attachment does on Huly

AI agents use update_lead_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 update_lead_attachment is rated Medium

Modifies attachment metadata (description, pinned state) reversibly within a CRM lead context.

From the tool's definition Update description or pinned state for an attachment only when it belongs to one exact lead.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_lead_attachment Rate-limited

update_lead_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": {
    "update_lead_attachment": {
      "limits": [
        {
          "counter": "update_lead_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 update_lead_attachment call is checked against it from then on.

FAQ

Questions about update_lead_attachment

What does the update_lead_attachment tool do? +

Update description or pinned state for an attachment only when it belongs to one exact lead. 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 update_lead_attachment? +

Register the Huly MCP server in PolicyLayer and add a rule for update_lead_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 update_lead_attachment? +

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

Can I rate-limit update_lead_attachment? +

Yes. Add a rate_limit block to the update_lead_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 update_lead_attachment completely? +

Set action: deny in the PolicyLayer policy for update_lead_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 update_lead_attachment? +

update_lead_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 600 Huly tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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