update_promotion
Update an existing promotion. Pass only the fields you want to change.
This record as markdown: /tools/io-favcrm-favcrm/update-promotion.md
What update_promotion does on FavCRM
AI agents use update_promotion 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 |
|---|---|---|---|
code | string | — | Promotion code |
name | string | — | Name |
type | string | — | Type |
value | string | — | Discount value (numeric or decimal string) |
endsAt | object | — | End timestamp (ISO 8601) |
status | string | — | Status filter |
startsAt | object | — | Start timestamp (ISO 8601) |
promotionId | string | Yes | Promotion ID |
usageLimitTotal | object | — | Total usage limit across all customers |
usageLimitPerCustomer | object | — | Usage limit per customer |
Parameters from the server's own tool schema.
Why update_promotion is rated Medium
This tool modifies promotion records in a CRM system. It is a Write operation because it creates or modifies data reversibly—promotions can be updated or corrected without permanent loss. It does not delete data (would be Destructive), execute external code (would be Execute), or move money (would be Financial).
From the tool's definition Tool name 'update_promotion' and description 'Update an existing promotion. Pass only the fields you want to change.' indicate modification of existing data.
Risk signalsAccepts freeform code/query input (code) · High parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs update_promotion 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_promotion, this is the rule to start with:
update_promotion 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_promotion call is checked against it from then on.
Questions about update_promotion
Update an existing promotion. Pass only the fields you want to change. 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_promotion accepts 10 parameters: code, name, type, value, endsAt, status, startsAt, promotionId, usageLimitTotal, usageLimitPerCustomer. Required: promotionId. 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_promotion: 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_promotion 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_promotion 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_promotion. 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_promotion 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