Update loyalty card information
AI agents use loyaltycard_update_loyalty_card to create or update resources in MCP Dynamics 365 Commerce Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Dynamics 365 Commerce Server environment.
This tool creates or modifies data reversibly within a customer loyalty system. While not destructive (changes can be undone/corrected), updating loyalty cards affects customer accounts and financial incentives, justifying high severity. An AI agent could maliciously alter loyalty points, tier status, or card details, impacting customer trust and business operations.
From the tool's definition Tool name contains 'update' and description states 'Update loyalty card information' — modifying customer loyalty data is a Write operation that can alter customer records and loyalty balances.
Attacks that exploit this kind of access
Update loyalty card information. It is categorised as a Write tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for loyaltycard_update_loyalty_card: 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_update_loyalty_card 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 loyaltycard_update_loyalty_card 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_update_loyalty_card. 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_update_loyalty_card 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 →