salesorder_send_receipt
Send transaction receipt to electronic addresses
This record as markdown: /tools/jiantmo-mcp-commerce/salesorder-send-receipt.md
What salesorder_send_receipt does on MCP Dynamics 365 Commerce Server
AI agents use salesorder_send_receipt 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 salesorder_send_receipt is rated Medium
This tool writes/sends data (receipt transmission) which could be reversed or resent, making it Write rather than Execute. While it triggers an external operation (sending), the primary effect is creating a communication record and delivery action. It is not Destructive (receipts can be resent), Financial (does not move money), or Read (creates side effects).
From the tool's definition The tool 'salesorder_send_receipt' performs an action that modifies state by sending a receipt to an electronic address.
Attacks that exploit this kind of access
The rule that runs salesorder_send_receipt 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 salesorder_send_receipt, this is the rule to start with:
salesorder_send_receipt 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 salesorder_send_receipt call is checked against it from then on.
Questions about salesorder_send_receipt
Send transaction receipt to electronic addresses. 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 salesorder_send_receipt: 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.
salesorder_send_receipt 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 salesorder_send_receipt 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 salesorder_send_receipt. 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.
salesorder_send_receipt 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