clone
Duplicate an existing record (product, tier, campaign, post, service package, promotion, gift offer). Creates a copy in DRAFT status with "(Copy)" appended to the name.
This record as markdown: /tools/io-favcrm-favcrm/clone.md
What clone does on FavCRM
AI agents use clone 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 |
|---|---|---|---|
name | string | — | Override the name of the cloned entity (defaults to "Original Name (Copy)") |
entityId | string | Yes | ID of the entity to clone |
entityType | string | Yes | Type of entity to clone |
Parameters from the server's own tool schema.
Why clone is rated Medium
The tool creates new records by duplicating existing ones (products, tiers, campaigns, posts, service packages, promotions, gift offers). This is a reversible write operation — the duplicated record can be modified or deleted. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool description states it 'Duplicate[s] an existing record' and 'Creates a copy in DRAFT status' — these are clear write operations that create new data records.
Attacks that exploit this kind of access
The rule that runs clone 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 clone, this is the rule to start with:
clone 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 clone call is checked against it from then on.
Questions about clone
Duplicate an existing record (product, tier, campaign, post, service package, promotion, gift offer). Creates a copy in DRAFT status with "(Copy)" appended to the name. 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.
clone accepts 3 parameters: name, entityId, entityType. Required: entityId, entityType. 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 clone: 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.
clone 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 clone 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 clone. 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.
clone 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