salesorder_checkin_for_order_pickup

WHAT IT DOES

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 IT NEEDS A POLICY

Why salesorder_checkin_for_order_pickup needs a policy

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)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

salesorder_checkin_for_order_pickup Rate-limited

salesorder_checkin_for_order_pickup stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Dynamics 365 Commerce Server, so you can run agents against it safely.

FAQ

Questions about salesorder_checkin_for_order_pickup

What does the salesorder_checkin_for_order_pickup tool do? +

Check in for order pickup. It is categorised as a Execute tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on salesorder_checkin_for_order_pickup? +

Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for salesorder_checkin_for_order_pickup: 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.

What risk level is salesorder_checkin_for_order_pickup? +

salesorder_checkin_for_order_pickup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit salesorder_checkin_for_order_pickup? +

Yes. Add a rate_limit block to the salesorder_checkin_for_order_pickup 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.

How do I block salesorder_checkin_for_order_pickup completely? +

Set action: deny in the PolicyLayer policy for salesorder_checkin_for_order_pickup. 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.

What MCP server provides salesorder_checkin_for_order_pickup? +

salesorder_checkin_for_order_pickup 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.