sales_orders_fulfillment_mark_as_picked
Updates status to Picked.
This record as markdown: /tools/jiantmo-mcp-commerce/sales-orders-fulfillment-mark-as-picked.md
What sales_orders_fulfillment_mark_as_picked does on MCP Dynamics 365 Commerce Server
AI agents use sales_orders_fulfillment_mark_as_picked 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 sales_orders_fulfillment_mark_as_picked is rated Medium
This tool creates or modifies data in a reversible manner by updating a sales order's fulfillment status. While it affects business operations, the change is not destructive or irreversible—the status can be changed again. It is not Financial (no money movement) and not Execute (no arbitrary code/commands).
From the tool's definition Tool name includes 'mark_as_picked' and description states 'Updates status to Picked' — this modifies the fulfillment state of sales orders, which is a write operation that changes order data reversibly (status can be updated to other values later).
Attacks that exploit this kind of access
The rule that runs sales_orders_fulfillment_mark_as_picked 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 sales_orders_fulfillment_mark_as_picked, this is the rule to start with:
sales_orders_fulfillment_mark_as_picked stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 sales_orders_fulfillment_mark_as_picked call is checked against it from then on.
Questions about sales_orders_fulfillment_mark_as_picked
Updates status to Picked. 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.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for sales_orders_fulfillment_mark_as_picked: 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.
sales_orders_fulfillment_mark_as_picked is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sales_orders_fulfillment_mark_as_picked 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 sales_orders_fulfillment_mark_as_picked. 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.
sales_orders_fulfillment_mark_as_picked 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