Resume a shift
AI agents invoke shifts_resume 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.
Resuming a shift is an operational action that changes the state of a shift (from paused/suspended to active). This is not a simple data read or write, but an execution of a business process/workflow transition. It has medium severity as it affects store operations and could impact financial reconciliation if misused, but is generally reversible (shifts can be paused again).
From the tool's definition 'Resume a shift' — triggers an operational state change on a shift object in the commerce system
Attacks that exploit this kind of access
Resume a 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_resume: 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_resume 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_resume 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_resume. 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_resume 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →