shifts_delete_shifts
Delete shifts (not supported in online context)
This record as markdown: /tools/jiantmo-mcp-commerce/shifts-delete-shifts.md
What shifts_delete_shifts does on MCP Dynamics 365 Commerce Server
AI agents call shifts_delete_shifts to permanently remove resources in MCP Dynamics 365 Commerce Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why shifts_delete_shifts is rated Critical
The tool performs a destructive operation by permanently removing shift records from the system. Even though the description notes it is 'not supported in online context', the tool's core function is to delete data irreversibly, which places it in the Destructive category. The severity is high because unauthorized deletion of shifts could disrupt workforce scheduling and business operations.
From the tool's definition Tool name contains 'delete' and description states 'Delete shifts' - this is an irreversible deletion operation that cannot be undone.
Attacks that exploit this kind of access
The rule that runs shifts_delete_shifts 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_delete_shifts, this is the rule to start with:
shifts_delete_shifts is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Dynamics 365 Commerce Server, apply this rule, and every shifts_delete_shifts call is checked against it from then on.
Questions about shifts_delete_shifts
Delete shifts (not supported in online context). It is categorised as a Destructive tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for shifts_delete_shifts: 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_delete_shifts is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the shifts_delete_shifts 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_delete_shifts. 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_delete_shifts 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