shifts_get_by_retrieval_criteria
Get shifts by retrieval criteria
This record as markdown: /tools/jiantmo-mcp-commerce/shifts-get-by-retrieval-criteria.md
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. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why shifts_get_by_retrieval_criteria is rated Low
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.
Attacks that exploit this kind of access
The rule that runs shifts_get_by_retrieval_criteria 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_get_by_retrieval_criteria, this is the rule to start with:
shifts_get_by_retrieval_criteria is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Dynamics 365 Commerce Server, apply this rule, and every shifts_get_by_retrieval_criteria call is checked against it from then on.
Questions about shifts_get_by_retrieval_criteria
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.
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.
shifts_get_by_retrieval_criteria is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
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.
More on MCP Dynamics 365 Commerce Server, and thousands of servers like it.
This server
Across the catalogue