earn_loyalty_points
Credit loyalty points or stamps to a member. Use field="points" for points, "stamps" for stamps. Server records a transaction with the reason as audit context.
This record as markdown: /tools/io-favcrm-favcrm/earn-loyalty-points.md
What earn_loyalty_points does on FavCRM
AI agents use earn_loyalty_points 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 |
|---|---|---|---|
field | string | Yes | Which loyalty unit to credit |
amount | integer | Yes | Positive integer amount to credit |
reason | string | — | Audit-trail reason (e.g. "Booking completed", "Manual adjustment") |
accountId | string | Yes | The member/account ID |
Parameters from the server's own tool schema.
Why earn_loyalty_points is rated Medium
This tool writes/creates loyalty transaction records by crediting points or stamps to member accounts. While it modifies data, it is not destructive (points can be reversed or adjusted), not financial (no money moves), and not an arbitrary execution.
From the tool's definition Tool description states: 'Credit loyalty points or stamps to a member' and 'Server records a transaction' — these are creation/modification operations that add value to customer accounts reversibly.
Attacks that exploit this kind of access
The rule that runs earn_loyalty_points 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 earn_loyalty_points, this is the rule to start with:
earn_loyalty_points 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 earn_loyalty_points call is checked against it from then on.
Questions about earn_loyalty_points
Credit loyalty points or stamps to a member. Use field="points" for points, "stamps" for stamps. Server records a transaction with the reason as audit context. 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.
earn_loyalty_points accepts 4 parameters: field, amount, reason, accountId. Required: field, amount, accountId. 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 earn_loyalty_points: 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.
earn_loyalty_points 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 earn_loyalty_points 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 earn_loyalty_points. 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.
earn_loyalty_points 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