salesorder_create_entity

WHAT IT DOES

What salesorder_create_entity does on MCP Dynamics 365 Commerce Server

AI agents use salesorder_create_entity 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 salesorder_create_entity needs a policy

This tool creates new sales orders, which are binding financial commitments that modify business data and trigger downstream fulfillment processes. While not a direct money movement (Financial), it's a high-severity Write operation because it commits orders that obligate the business and affect inventory, revenue recognition, and customer accounts. Misuse could create fraudulent orders or disrupt order processing.

From the tool's definition Tool name 'salesorder_create_entity' and description 'Upload a booked sales order with tender lines' indicate creation of sales order records with payment/tender information.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

salesorder_create_entity Rate-limited

salesorder_create_entity 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": {
    "salesorder_create_entity": {
      "limits": [
        {
          "counter": "salesorder_create_entity_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 salesorder_create_entity

What does the salesorder_create_entity tool do? +

Upload a booked sales order with tender lines. 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 salesorder_create_entity? +

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

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

Can I rate-limit salesorder_create_entity? +

Yes. Add a rate_limit block to the salesorder_create_entity 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 salesorder_create_entity completely? +

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

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