Get sales order by transaction identifier
AI agents call salesorder_get_entity_by_key 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 an existing sales order using a transaction identifier as a lookup key. There is no modification, deletion, or execution of external operations—it simply queries and returns data. This is a straightforward Read operation with low risk and a narrow blast radius (information disclosure only).
From the tool's definition Tool name 'salesorder_get_entity_by_key' and description 'Get sales order by transaction identifier' indicate a retrieval operation. The verb 'Get' and pattern of querying by key are characteristic of read-only data retrieval with no side effects.
Attacks that exploit this kind of access
Get sales order by transaction 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_get_entity_by_key: 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_get_entity_by_key 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_get_entity_by_key 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_get_entity_by_key. 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_get_entity_by_key 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 →