products_update_price_by_id_for_product

Update Price by ID for a Product

SERVERGhl SOURCE@aiwerk/mcp-server-ghl

Medium RISK CLASS

Category Write

Parameters 126 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-price-by-id-for-product.md

WHAT IT DOES

What products_update_price_by_id_for_product does on Ghl

AI agents use products_update_price_by_id_for_product 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
`sku`	string	—	The unique identifier of the SKU associated with the price
`meta`	object	—	Additional metadata associated with the price.
`name`	string	Yes	The name of the price.
`type`	string	Yes	The type of the price.
`amount`	number	Yes	The amount of the price. ( min: 0 )
`userId`	string	—	The unique identifier of the user who created the price.
`priceId`	string	Yes	ID of the price that needs to be returned
`currency`	string	Yes	The currency of the price.
`setupFee`	number	—	The setup fee for the price.
`productId`	string	Yes	ID of the product that needs to be used
`recurring`	object	—	The recurring details of the price (if type is recurring).
`locationId`	string	—	The unique identifier of the location associated with the price. Defaults to GHL_LOCATION_ID when omitted.

Parameters from the server's own tool schema.

RISK

Why products_update_price_by_id_for_product is rated Medium

An AI agent can call products_update_price_by_id_for_product 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 (32 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

products_update_price_by_id_for_product Rate-limited

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

FAQ

Questions about products_update_price_by_id_for_product

What does the products_update_price_by_id_for_product tool do? +

Update Price by ID for a Product. 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_price_by_id_for_product accept? +

products_update_price_by_id_for_product accepts 12 parameters: sku, meta, name, type, amount, userId, priceId, currency, setupFee, productId, recurring, locationId. Required: name, type, amount, priceId, currency, 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_price_by_id_for_product? +

Register the Ghl MCP server in PolicyLayer and add a rule for products_update_price_by_id_for_product: 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_price_by_id_for_product? +

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

Can I rate-limit products_update_price_by_id_for_product? +

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

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

products_update_price_by_id_for_product 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 →