Transfer points between loyalty cards
AI agents use loyaltycard_transfer_points to commit financial operations through MCP Dynamics 365 Commerce Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Transferring loyalty points between accounts constitutes moving financial value/obligations. Loyalty points have real monetary worth and can be redeemed for goods, discounts, or cash equivalents. Misuse could result in unauthorized transfer of financial value between accounts, making this a Financial category tool with high severity.
From the tool's definition Transfer points between loyalty cards
Attacks that exploit this kind of access
Transfer points between loyalty cards. It is categorised as a Financial tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for loyaltycard_transfer_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 MCP Dynamics 365 Commerce Server. Nothing to install.
loyaltycard_transfer_points is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the loyaltycard_transfer_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 loyaltycard_transfer_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.
loyaltycard_transfer_points is provided by the MCP Dynamics 365 Commerce Server MCP server (jiantmo/mcp-commerce). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →