products_update_product_by_id

Update Product by ID

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 122 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/products-update-product-by-id.md

WHAT IT DOES

What products_update_product_by_id does on Ghl

AI agents use products_update_product_by_id to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.

Parameter	Type	Required	Description
`seo`	object	—	SEO data for the product that will be displayed in the preview
`name`	string	Yes	The name of the product.
`slug`	string	—	The slug using which the product navigation will be handled
`image`	string	—	The URL for the product image.
`label`	object	—	Details for Product Label
`taxes`	array	—	List of ids of Taxes attached to the Product. If taxes are passed, isTaxesEnabled should be true.
`medias`	array	—	An array of medias for the product.
`prices`	array	—	The prices of the product
`variants`	array	—	An array of variants for the product.
`productId`	string	Yes	ID or the slug of the product that needs to be returned
`locationId`	string	—	The unique identifier for the location. Defaults to GHL_LOCATION_ID when omitted.
`description`	string	—	A brief description of the product.

Parameters from the server's own tool schema.

RISK

Why products_update_product_by_id is rated Medium

An AI agent can call products_update_product_by_id faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (25 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs products_update_product_by_id safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Ghl, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For products_update_product_by_id, this is the rule to start with:

products_update_product_by_id Rate-limited

products_update_product_by_id 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": {
    "products_update_product_by_id": {
      "limits": [
        {
          "counter": "products_update_product_by_id_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 Ghl, apply this rule, and every products_update_product_by_id call is checked against it from then on.

FAQ

Questions about products_update_product_by_id

What does the products_update_product_by_id tool do? +

Update Product by ID. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does products_update_product_by_id accept? +

products_update_product_by_id accepts 12 parameters: seo, name, slug, image, label, taxes, medias, prices, variants, productId, locationId, description. Required: name, productId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on products_update_product_by_id? +

Register the Ghl MCP server in PolicyLayer and add a rule for products_update_product_by_id: 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 Ghl. Nothing to install.

What risk level is products_update_product_by_id? +

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

Can I rate-limit products_update_product_by_id? +

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

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

products_update_product_by_id is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Ghl, and thousands of servers like it.

This server

All 569 Ghl 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 →