Update cart lines in cart
AI agents use cart_update_cart_lines 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.
The tool modifies shopping cart contents, which affects order state and customer checkout flow. While reversible (items can be re-added), unauthorized updates could manipulate pricing, remove items, or alter orders in progress. High severity due to direct customer-facing impact and transaction integrity implications.
From the tool's definition Tool name contains 'update' and description states 'Update cart lines in cart' — this modifies cart data (items, quantities, prices) reversibly.
Attacks that exploit this kind of access
Update cart lines in cart. 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 cart_update_cart_lines: 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_update_cart_lines 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 cart_update_cart_lines 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_update_cart_lines. 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_update_cart_lines 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 →