New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

shifts_force_delete

Forcefully delete a shift

SERVERMCP Dynamics 365 Commerce Server SOURCEjiantmo/mcp-commerce
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jiantmo-mcp-commerce/shifts-force-delete.md

What shifts_force_delete does on MCP Dynamics 365 Commerce Server

AI agents call shifts_force_delete 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_force_delete is rated Critical

Deletion is inherently destructive and cannot be undone. The word 'force' emphasizes that the operation bypasses normal safeguards. The blast radius is high in a retail/commerce context: deleting a shift affects employee scheduling, payroll records, and operational continuity.

From the tool's definition Tool name contains 'force_delete' and description states 'Forcefully delete a shift' — both explicitly indicate irreversible deletion of data.

Questions about shifts_force_delete

What does the shifts_force_delete tool do? +

Forcefully delete a shift. 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.

How do I enforce a policy on shifts_force_delete? +

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

shifts_force_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit shifts_force_delete? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MCP Dynamics 365 Commerce Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.