salesorder_search_transactions_by_receipt_paged
Search sales transactions by receipt identifier with paging support
This record as markdown: /tools/jiantmo-mcp-commerce/salesorder-search-transactions-by-receipt-paged.md
What salesorder_search_transactions_by_receipt_paged does on MCP Dynamics 365 Commerce Server
AI agents call salesorder_search_transactions_by_receipt_paged 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_paged is rated Low
This tool performs a data retrieval operation querying sales transactions filtered by receipt identifier. The presence of 'paging support' confirms it is a read-only search function designed to fetch existing transaction records. There is no indication of creation, modification, deletion, or execution of external operations.
From the tool's definition Tool name contains 'search' and description states 'Search sales transactions by receipt identifier' — a query operation that retrieves data without modification.
Attacks that exploit this kind of access
The rule that runs salesorder_search_transactions_by_receipt_paged 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_paged, this is the rule to start with:
salesorder_search_transactions_by_receipt_paged 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_paged call is checked against it from then on.
Questions about salesorder_search_transactions_by_receipt_paged
Search sales transactions by receipt identifier with paging support. 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_paged: 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_paged 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_paged 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_paged. 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_paged 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