shifts_upsert_and_validate_shifts

Insert or update and validate shifts

Server MCP Dynamics 365 Commerce Server jiantmo/mcp-commerce
Category Write
Risk class Medium
Parameters 00 required

What shifts_upsert_and_validate_shifts does on MCP Dynamics 365 Commerce Server

AI agents use shifts_upsert_and_validate_shifts 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_upsert_and_validate_shifts needs a policy

This tool creates or modifies shift records reversibly (shifts can be edited or deleted later). It does not execute arbitrary code, delete permanently, move money, or retrieve data without side effects. The 'validate' component is a safety check, not a separate category. In a commerce system, shifts likely refer to employee work schedules or store operating hours.

From the tool's definition Tool name contains 'upsert_and_validate' which indicates create-or-update operations on shift data. 'Upsert' is a standard database operation combining insert and update, affecting shift records in a commerce/workforce management context.

Questions about shifts_upsert_and_validate_shifts

What does the shifts_upsert_and_validate_shifts tool do? +

Insert or update and validate shifts. 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.

How do I enforce a policy on shifts_upsert_and_validate_shifts? +

Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for shifts_upsert_and_validate_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.

What risk level is shifts_upsert_and_validate_shifts? +

shifts_upsert_and_validate_shifts is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit shifts_upsert_and_validate_shifts? +

Yes. Add a rate_limit block to the shifts_upsert_and_validate_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.

How do I block shifts_upsert_and_validate_shifts completely? +

Set action: deny in the PolicyLayer policy for shifts_upsert_and_validate_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.

What MCP server provides shifts_upsert_and_validate_shifts? +

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

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.