transfer_order_commit · MCP Dynamics 365 Commerce Server MCP

WHAT IT DOES

What transfer_order_commit does on MCP Dynamics 365 Commerce Server

AI agents use transfer_order_commit to create or update resources in MCP Dynamics 365 Commerce Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Dynamics 365 Commerce Server environment.

WHY IT NEEDS A POLICY

Why transfer_order_commit needs a policy

Committing a transfer order is a significant write operation that finalizes inventory movement between store/warehouse locations. While potentially reversible through reversal procedures, it changes inventory records and triggers downstream processes. It does not delete data, execute arbitrary code, or move money, making Write the most appropriate category.

From the tool's definition 'Commits a transfer order' — committing a transfer order finalizes the movement of inventory between locations in Dynamics 365 Commerce

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

transfer_order_commit Rate-limited

transfer_order_commit stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_order_commit": {
      "limits": [
        {
          "counter": "transfer_order_commit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Dynamics 365 Commerce Server, so you can run agents against it safely.

FAQ

Questions about transfer_order_commit

What does the transfer_order_commit tool do? +

Commits a transfer order. It is categorised as a Write tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on transfer_order_commit? +

Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for transfer_order_commit: 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.

What risk level is transfer_order_commit? +

transfer_order_commit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit transfer_order_commit? +

Yes. Add a rate_limit block to the transfer_order_commit 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.

How do I block transfer_order_commit completely? +

Set action: deny in the PolicyLayer policy for transfer_order_commit. 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.

What MCP server provides transfer_order_commit? +

transfer_order_commit 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.