transfer_order_get_entity_by_key
Gets transfer order by id.
This record as markdown: /tools/jiantmo-mcp-commerce/transfer-order-get-entity-by-key.md
What transfer_order_get_entity_by_key does on MCP Dynamics 365 Commerce Server
AI agents call transfer_order_get_entity_by_key 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 transfer_order_get_entity_by_key is rated Low
This tool retrieves a transfer order record by its identifier. It is a read-only query operation that returns existing data without side effects, modifications, or destructive actions. The low severity reflects minimal blast radius - an AI agent misusing this tool could only access transfer order information already stored in the system, with no ability to alter, delete, or execute operations.
From the tool's definition Tool name contains 'get' and description states 'Gets transfer order by id' - a straightforward data retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
The rule that runs transfer_order_get_entity_by_key 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 transfer_order_get_entity_by_key, this is the rule to start with:
transfer_order_get_entity_by_key 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 transfer_order_get_entity_by_key call is checked against it from then on.
Questions about transfer_order_get_entity_by_key
Gets transfer 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 transfer_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.
transfer_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 transfer_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 transfer_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.
transfer_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.
More on MCP Dynamics 365 Commerce Server, and thousands of servers like it.
This server
Across the catalogue