This record as markdown: /tools/jiantmo-mcp-commerce/shifts-close.md
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 shifts_close is rated Medium
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
The rule that runs shifts_close 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_close, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Dynamics 365 Commerce Server, apply this rule, and every shifts_close call is checked against it from then on.
Questions about shifts_close
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.
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.
shifts_close is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on MCP Dynamics 365 Commerce Server, and thousands of servers like it.
This server
Across the catalogue