shifts_upsert_and_validate_shifts

What shifts_upsert_and_validate_shifts does on MCP Dynamics 365 Commerce Server

AI agents use shifts_upsert_and_validate_shifts 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 shifts_upsert_and_validate_shifts is rated Medium

This tool creates or modifies shift records reversibly (shifts can be edited or deleted later). It does not execute arbitrary code, delete permanently, move money, or retrieve data without side effects. The 'validate' component is a safety check, not a separate category. In a commerce system, shifts likely refer to employee work schedules or store operating hours.

From the tool's definition Tool name contains 'upsert_and_validate' which indicates create-or-update operations on shift data. 'Upsert' is a standard database operation combining insert and update, affecting shift records in a commerce/workforce management context.

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "shifts_upsert_and_validate_shifts": {
      "limits": [
        {
          "counter": "shifts_upsert_and_validate_shifts_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about shifts_upsert_and_validate_shifts