shifts_close · MCP Dynamics 365 Commerce Server MCP

WHAT IT DOES

What shifts_close does on MCP Dynamics 365 Commerce Server

AI agents use shifts_close 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_close needs a policy

Closing a shift modifies data state but is reversible (shifts can typically be reopened or adjusted). This is a Write operation rather than Destructive since it doesn't permanently delete or irreversibly destroy data. Severity is medium because misuse could disrupt retail operations, financial reconciliation, and employee records, but the action itself is not destructive and can be corrected.

From the tool's definition Tool name 'shifts_close' and description 'Close a shift' indicate an action that modifies the state of a shift record (from open to closed), which is a reversible operational change in a retail/commerce system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

shifts_close Rate-limited

shifts_close 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_close": {
      "limits": [
        {
          "counter": "shifts_close_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_close

What does the shifts_close tool do? +

Close a 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_close? +

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

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

Can I rate-limit shifts_close? +

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

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

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