cart_update_line_delivery_specifications
Update line delivery specifications
This record as markdown: /tools/jiantmo-mcp-commerce/cart-update-line-delivery-specifications.md
What cart_update_line_delivery_specifications does on MCP Dynamics 365 Commerce Server
AI agents use cart_update_line_delivery_specifications 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_update_line_delivery_specifications is rated Medium
The tool creates or modifies cart data reversibly. While carts can contain financial implications (orders), the tool itself only updates delivery specifications, not payment or order completion. Misclassification as Execute would require evidence of arbitrary code execution or system commands, which is absent.
From the tool's definition Tool name contains 'update' and description states 'Update line delivery specifications'. This modifies cart line items' delivery details (address, method, timing, etc.) in a reversible manner without deleting data or executing arbitrary code.
Attacks that exploit this kind of access
The rule that runs cart_update_line_delivery_specifications 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_update_line_delivery_specifications, this is the rule to start with:
cart_update_line_delivery_specifications 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_update_line_delivery_specifications call is checked against it from then on.
Questions about cart_update_line_delivery_specifications
Update line delivery specifications. 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_line_delivery_specifications: 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_line_delivery_specifications 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_line_delivery_specifications 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_line_delivery_specifications. 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_line_delivery_specifications 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