Checkout the cart
AI agents use cart_checkout 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.
Checking out a cart in an e-commerce system like Dynamics 365 Commerce finalizes a purchase, committing financial obligations (payment processing, order creation). This is the most severe category applicable as it directly involves financial transactions. Misuse could result in unauthorized purchases or financial commitments.
From the tool's definition 'cart_checkout' - 'Checkout the cart' commits a financial transaction by converting a cart into a sales order with payment obligations
Attacks that exploit this kind of access
Checkout the cart. 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 cart_checkout: 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.
cart_checkout 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 cart_checkout 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 cart_checkout. 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.
cart_checkout 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 →