Get shifts by status filtered by user role
AI agents call shifts_get_by_status_filter_by_user_role 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.
This tool retrieves shift information filtered by status and user role—a read-only operation that queries existing data without creating, modifying, deleting, or executing external operations. The low severity reflects minimal blast radius if misused by an agent, as it only exposes existing shift records visible to the querying user role.
From the tool's definition Tool name 'shifts_get_by_status_filter_by_user_role' uses 'get' verb indicating data retrieval. Description 'Get shifts by status filtered by user role' confirms it retrieves/queries shift data without modification or side effects.
Attacks that exploit this kind of access
Get shifts by status filtered by user role. 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_status_filter_by_user_role: 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_status_filter_by_user_role 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_status_filter_by_user_role 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_status_filter_by_user_role. 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_status_filter_by_user_role 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.
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 →