salesorder_checkin_for_order_pickup

What salesorder_checkin_for_order_pickup does on MCP Dynamics 365 Commerce Server

AI agents invoke salesorder_checkin_for_order_pickup to trigger actions in MCP Dynamics 365 Commerce Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why salesorder_checkin_for_order_pickup is rated High

This tool performs a state-change operation on a sales order in an external system. It is not a simple read, nor does it create/modify data in a reversible write sense — it triggers a workflow event (check-in) that notifies store staff and changes order status. This qualifies as Execute due to triggering external operational effects. Misuse could cause confusion in order fulfillment workflows, hence medium severity.

From the tool's definition 'Check in for order pickup' — triggers an external operation in the Dynamics 365 Commerce system that changes the state of a sales order (marking it as checked in for pickup)

The rule that runs salesorder_checkin_for_order_pickup 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 salesorder_checkin_for_order_pickup, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "salesorder_checkin_for_order_pickup": {
      "limits": [
        {
          "counter": "salesorder_checkin_for_order_pickup_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about salesorder_checkin_for_order_pickup