commit_customer_import
Commit a previewed customer import. Pass the same rows and sessionId returned by preview_customer_import. Creates/updates accounts and applies points, stamps, and credit deltas.
This record as markdown: /tools/io-favcrm-favcrm/commit-customer-import.md
What commit_customer_import does on FavCRM
AI agents use commit_customer_import 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 |
|---|---|---|---|
rows | array | Yes | |
sessionId | string | Yes | sessionId from preview_customer_import |
Parameters from the server's own tool schema.
Why commit_customer_import is rated Medium
This tool creates and updates customer accounts and modifies associated data (loyalty points, stamps, credit balances). While these are reversible operations in principle (accounts can be updated or corrected), the tool makes material changes to customer financial state (credit deltas) and loyalty program status. The use of 'commit' suggests this finalizes a bulk operation.
From the tool's definition Tool description states it "Creates/updates accounts and applies points, stamps, and credit deltas" — modifying customer data, loyalty program state, and account credits.
Risk signalsHigh parameter count (23 properties)
Attacks that exploit this kind of access
The rule that runs commit_customer_import 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 commit_customer_import, this is the rule to start with:
commit_customer_import 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 commit_customer_import call is checked against it from then on.
Questions about commit_customer_import
Commit a previewed customer import. Pass the same rows and sessionId returned by preview_customer_import. Creates/updates accounts and applies points, stamps, and credit deltas. 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.
commit_customer_import accepts 2 parameters: rows, sessionId. Required: rows, sessionId. 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 commit_customer_import: 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.
commit_customer_import 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 commit_customer_import 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 commit_customer_import. 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.
commit_customer_import 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