restore_promotion
Restore a previously deleted promotion.
This record as markdown: /tools/io-favcrm-favcrm/restore-promotion.md
What restore_promotion does on FavCRM
AI agents use restore_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 |
|---|---|---|---|
promotionId | string | Yes | Promotion ID |
Parameters from the server's own tool schema.
Why restore_promotion is rated Medium
While restoration might seem similar to Destructive (which is typically applied to irreversible deletions), this tool does the opposite—it reverses a deletion and restores data. This is a Write operation because it creates or modifies data reversibly. The severity is medium because misuse could create unintended promotions affecting business operations, but the effect is recoverable by re-deleting the promotion.
From the tool's definition The tool name is 'restore_promotion' and the description states it 'Restore[s] a previously deleted promotion.' This reverses a deletion operation by recreating a promotion that was previously removed, modifying the data state.
Attacks that exploit this kind of access
The rule that runs restore_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 restore_promotion, this is the rule to start with:
restore_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 restore_promotion call is checked against it from then on.
Questions about restore_promotion
Restore a previously deleted promotion. 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.
restore_promotion accepts 1 parameter: promotionId. 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 restore_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.
restore_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 restore_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 restore_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.
restore_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