Block or unblock a loyalty card
AI agents use loyaltycard_block_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.
Blocking or unblocking a loyalty card is a reversible state change (it can be unblocked), making it a Write operation. However, the severity is high because blocking a card can immediately prevent a customer from redeeming rewards or making purchases, creating significant customer impact if misused by an AI agent.
From the tool's definition 'Block or unblock a loyalty card' — modifies the state of a loyalty card (blocking/unblocking access)
Attacks that exploit this kind of access
Block or unblock a loyalty card. 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_block_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_block_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_block_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_block_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_block_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 →