issue_rewards
Issue a gift/reward to multiple members. Requires a gift offer ID and member IDs.
This record as markdown: /tools/io-favcrm-favcrm/issue-rewards.md
What issue_rewards does on FavCRM
AI agents use issue_rewards 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 |
|---|---|---|---|
expiresAt | string | — | Optional ISO date when the reward expires |
memberIds | array | Yes | Member/account IDs to receive the reward (max 50) |
giftOfferId | string | Yes | The gift offer/reward scheme ID to issue |
Parameters from the server's own tool schema.
Why issue_rewards is rated Medium
This tool modifies customer loyalty/reward data by issuing gifts or rewards to member accounts. It is a write operation that creates new reward records and adjusts member balances or entitlements. While reversible (rewards can typically be voided or adjusted), it represents a material change to customer data and financial standing within the loyalty program.
From the tool's definition Tool name 'issue_rewards' combined with description stating it 'Issue a gift/reward to multiple members' indicates creation/modification of reward records and loyalty account states.
Attacks that exploit this kind of access
The rule that runs issue_rewards 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 issue_rewards, this is the rule to start with:
issue_rewards 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 issue_rewards call is checked against it from then on.
Questions about issue_rewards
Issue a gift/reward to multiple members. Requires a gift offer ID and member IDs. 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.
issue_rewards accepts 3 parameters: expiresAt, memberIds, giftOfferId. Required: memberIds, giftOfferId. 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 issue_rewards: 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.
issue_rewards 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 issue_rewards 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 issue_rewards. 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.
issue_rewards 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