Get a purchase order by id.
AI agents call purchase_order_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 a specific purchase order record by its identifier. It performs a query operation with no side effects—it does not create, modify, delete, or execute any operations. The data returned is informational only. Severity is low because reading purchase order data, while potentially sensitive, does not directly impact system integrity or enable financial transactions by itself.
From the tool's definition Tool name 'get_entity_by_key' and description 'Get a purchase order by id' indicate a retrieval operation with no modification capability. The verb 'Get' is a standard read operation.
Attacks that exploit this kind of access
Get a purchase order by id. 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 purchase_order_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.
purchase_order_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 purchase_order_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 purchase_order_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.
purchase_order_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 →