This record as markdown: /tools/jiantmo-mcp-commerce/shifts-use.md
What shifts_use does on MCP Dynamics 365 Commerce Server
AI agents invoke shifts_use 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 shifts_use is rated High
'Using' a shift in a retail/commerce context typically means activating or claiming an open shift, which triggers external operations in the POS/store system (e.g., associating a cashier with a register, enabling transaction processing). This is an action with real operational side effects rather than a simple read or reversible write.
From the tool's definition 'Use an existing shift' — activates or applies an existing shift record in Dynamics 365 Commerce
Attacks that exploit this kind of access
The rule that runs shifts_use 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_use, this is the rule to start with:
shifts_use 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.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Dynamics 365 Commerce Server, apply this rule, and every shifts_use call is checked against it from then on.
Questions about shifts_use
Use an existing shift. 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.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for shifts_use: 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_use is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the shifts_use 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_use. 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_use 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.
Across the catalogue