update_inventory_variant

Rename and/or change the SKU of an inventory variant. variant accepts ID, exact name, or exact SKU; pass product when needed. Rejects duplicate names or SKUs in the same product.

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-inventory-variant.md

WHAT IT DOES

What update_inventory_variant does on Huly

AI agents use update_inventory_variant 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_inventory_variant is rated Medium

This tool modifies inventory variant metadata (name and SKU) but does not delete or irreversibly destroy data. The operation is reversible—names and SKUs can be changed back. It is not Destructive (no deletion), not Execute (no arbitrary code/command execution), not Financial (no money movement), and not Read (it writes/modifies data).

From the tool's definition Tool description explicitly states 'Rename and/or change the SKU of an inventory variant', indicating modification of existing inventory data. The phrases 'Rename' and 'change' are reversible write operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_inventory_variant Rate-limited

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

FAQ

Questions about update_inventory_variant

What does the update_inventory_variant tool do? +

Rename and/or change the SKU of an inventory variant. variant accepts ID, exact name, or exact SKU; pass product when needed. Rejects duplicate names or SKUs in the same product. 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_inventory_variant? +

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

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

Can I rate-limit update_inventory_variant? +

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

Set action: deny in the PolicyLayer policy for update_inventory_variant. 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_inventory_variant? +

update_inventory_variant 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

emit_variant_plan on 0sec →aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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