shifts_patch_shift · MCP Dynamics 365 Commerce Server MCP

WHAT IT DOES

What shifts_patch_shift does on MCP Dynamics 365 Commerce Server

AI agents use shifts_patch_shift 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 IT NEEDS A POLICY

Why shifts_patch_shift needs a policy

This tool modifies existing shift records in the Dynamics 365 Commerce system. It is reversible (shifts can be corrected or modified again) and does not permanently destroy data or execute arbitrary code. It falls under Write category. Severity is medium because incorrect shift updates could affect scheduling and operations, but the impact is bounded to shift management and the operation is reversible.

From the tool's definition Tool name 'shifts_patch_shift' and description 'Handle PATCH requests to update existing shift' indicate modification of shift data. PATCH is a standard HTTP method for partial updates to resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

shifts_patch_shift Rate-limited

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

View as policy code

policy.json

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

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 shifts_patch_shift

What does the shifts_patch_shift tool do? +

Handle PATCH requests to update existing shift. 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.

How do I enforce a policy on shifts_patch_shift? +

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

shifts_patch_shift is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit shifts_patch_shift? +

Yes. Add a rate_limit block to the shifts_patch_shift 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 shifts_patch_shift completely? +

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

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