Void suspended transactions for a shift
AI agents call shifts_void_suspended_carts to permanently remove resources in MCP Dynamics 365 Commerce Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Voiding transactions in a commerce system is a destructive, irreversible action. Once a suspended cart/transaction is voided, it cannot be recovered. This has significant business impact as it permanently removes pending sales transactions associated with a shift.
From the tool's definition 'Void suspended transactions' — voiding transactions is an irreversible operation that cancels/nullifies suspended cart data
Attacks that exploit this kind of access
Void suspended transactions for a shift. It is categorised as a Destructive tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for shifts_void_suspended_carts: 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.
shifts_void_suspended_carts is a Destructive 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 shifts_void_suspended_carts 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 shifts_void_suspended_carts. 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.
shifts_void_suspended_carts 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 →