shifts_get_by_retrieval_criteria

Get shifts by retrieval criteria

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

What shifts_get_by_retrieval_criteria does on MCP Dynamics 365 Commerce Server

AI agents call shifts_get_by_retrieval_criteria to retrieve information from MCP Dynamics 365 Commerce Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why shifts_get_by_retrieval_criteria needs a policy

This tool retrieves shift information based on specified criteria. The 'get' verb and absence of any modification, deletion, or execution language clearly indicates a read-only operation. No side effects or destructive actions are implied. The severity is low as retrieving shift data poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name contains 'get_by' and description states 'Get shifts by retrieval criteria' - indicates querying/retrieving shift data without modification or deletion.

Questions about shifts_get_by_retrieval_criteria

What does the shifts_get_by_retrieval_criteria tool do? +

Get shifts by retrieval criteria. It is categorised as a Read tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on shifts_get_by_retrieval_criteria? +

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

shifts_get_by_retrieval_criteria is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit shifts_get_by_retrieval_criteria? +

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

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

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