update_product
Update an existing product. Only provided fields are changed.
This record as markdown: /tools/io-favcrm-favcrm/update-product.md
What update_product does on FavCRM
AI agents use update_product to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
sku | string | — | SKU code |
name | string | — | Product name |
price | string | — | Price as decimal string |
status | string | — | Product status |
productId | number | Yes | The product ID |
categoryIds | array | — | Category IDs (first is primary). Replaces all existing categories. |
description | string | — | Product description |
memberPrice | string | — | Members-only price |
discountPrice | string | — | Discounted price |
Parameters from the server's own tool schema.
Why update_product is rated Medium
This tool modifies product data within the CRM system but does not delete or irreversibly destroy information. The effect is reversible—updated fields can be changed again. It does not execute arbitrary code, trigger external operations with unpredictable effects, move money, or destroy data. It falls squarely into the Write category as a data modification operation.
From the tool's definition Tool name 'update_product' and description 'Update an existing product. Only provided fields are changed.' indicate modification of existing data in a reversible manner.
Attacks that exploit this kind of access
The rule that runs update_product safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_product, this is the rule to start with:
update_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.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every update_product call is checked against it from then on.
Questions about update_product
Update an existing product. Only provided fields are changed. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_product accepts 9 parameters: sku, name, price, status, productId, categoryIds, description, memberPrice, discountPrice. Required: productId. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for update_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 FavCRM. Nothing to install.
update_product is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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.
Set action: deny in the PolicyLayer policy for update_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.
update_product is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue