purchase_order_patch_entity

WHAT IT DOES

What purchase_order_patch_entity does on MCP Dynamics 365 Commerce Server

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

This tool modifies purchase order data in persistent storage (local database). It is reversible (data can be corrected or rolled back in subsequent operations), so it does not qualify as Destructive. It does not involve financial transactions themselves, though purchase orders are financial instruments—the tool's function is data modification, not money movement.

From the tool's definition Tool name 'patch_entity' and description 'Saves a purchase order to local database' indicate modifying/persisting data. 'Patch' typically implies updating an existing entity; 'Saves' confirms data persistence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

purchase_order_patch_entity Rate-limited

purchase_order_patch_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": {
    "purchase_order_patch_entity": {
      "limits": [
        {
          "counter": "purchase_order_patch_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 purchase_order_patch_entity

What does the purchase_order_patch_entity tool do? +

Saves a purchase order to local database. 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_patch_entity? +

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

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

Can I rate-limit purchase_order_patch_entity? +

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

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

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