purchase_order_commit · MCP Dynamics 365 Commerce Server MCP

WHAT IT DOES

What purchase_order_commit does on MCP Dynamics 365 Commerce Server

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

Committing a purchase order is a Write/Execute action that finalizes a procurement transaction, making it binding. It does not directly move money (no payment execution), but it creates a formal obligation to purchase goods/services. It is not purely destructive. The highest applicable category is Write, though the financial implications of committing procurement obligations push severity to high.

From the tool's definition 'Commits a purchase order' — finalizing/committing a purchase order creates a binding procurement record in the system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

purchase_order_commit Rate-limited

purchase_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": {
    "purchase_order_commit": {
      "limits": [
        {
          "counter": "purchase_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 purchase_order_commit

What does the purchase_order_commit tool do? +

Commits a purchase 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 purchase_order_commit? +

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

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

Can I rate-limit purchase_order_commit? +

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

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

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