cart_merge_carts
Merge multiple carts
This record as markdown: /tools/jiantmo-mcp-commerce/cart-merge-carts.md
What cart_merge_carts does on MCP Dynamics 365 Commerce Server
AI agents use cart_merge_carts 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.
Why cart_merge_carts is rated Medium
This tool modifies existing cart data by consolidating multiple carts into one, which is a Write-category action. Severity is medium rather than high because: (1) the operation is reversible (carts can typically be recreated or separated), (2) it affects transactional user data (shopping carts) rather than system-critical data, and (3) misuse by an AI agent could cause inconvenience (wrong carts merged) but not…
From the tool's definition Tool name 'cart_merge_carts' and description 'Merge multiple carts' indicate a data modification operation that combines cart entities. Merging is a reversible write operation that modifies cart state.
Attacks that exploit this kind of access
The rule that runs cart_merge_carts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Dynamics 365 Commerce Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cart_merge_carts, this is the rule to start with:
cart_merge_carts stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Dynamics 365 Commerce Server, apply this rule, and every cart_merge_carts call is checked against it from then on.
Questions about cart_merge_carts
Merge multiple carts. 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_merge_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.
cart_merge_carts 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_merge_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 cart_merge_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.
cart_merge_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.
More on MCP Dynamics 365 Commerce Server, and thousands of servers like it.
This server
Across the catalogue