salesorder_search_transactions_by_receipt
Search sales transactions by receipt identifier
This record as markdown: /tools/jiantmo-mcp-commerce/salesorder-search-transactions-by-receipt.md
What salesorder_search_transactions_by_receipt does on MCP Dynamics 365 Commerce Server
AI agents call salesorder_search_transactions_by_receipt 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 salesorder_search_transactions_by_receipt is rated Low
This tool retrieves or queries sales transaction data based on a receipt ID. It performs a lookup operation with no side effects—no data is created, modified, deleted, or executed. The action is read-only and returns information for analysis. The blast radius of misuse is minimal; an agent could only retrieve transaction records it has access to, which presents low risk.
From the tool's definition Tool name 'search_transactions_by_receipt' and description 'Search sales transactions by receipt identifier' indicate a query/retrieval operation with no modification of data.
Attacks that exploit this kind of access
The rule that runs salesorder_search_transactions_by_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_search_transactions_by_receipt, this is the rule to start with:
salesorder_search_transactions_by_receipt 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 salesorder_search_transactions_by_receipt call is checked against it from then on.
Questions about salesorder_search_transactions_by_receipt
Search sales transactions by receipt identifier. 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 salesorder_search_transactions_by_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_search_transactions_by_receipt 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 salesorder_search_transactions_by_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_search_transactions_by_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_search_transactions_by_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