non_sales_tender_create_transaction

WHAT IT DOES

What non_sales_tender_create_transaction does on MCP Dynamics 365 Commerce Server

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

This tool creates new transaction records, which is a write operation that modifies system state. However, it is scoped to non-sales transactions (e.g., adjustments, refunds, tender operations) rather than financial movements, and appears reversible through other operations.

From the tool's definition Tool name 'non_sales_tender_create_transaction' and description 'Creates non-sales transaction' indicate the tool creates/modifies transaction records in a commerce system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

non_sales_tender_create_transaction Rate-limited

non_sales_tender_create_transaction 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": {
    "non_sales_tender_create_transaction": {
      "limits": [
        {
          "counter": "non_sales_tender_create_transaction_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 non_sales_tender_create_transaction

What does the non_sales_tender_create_transaction tool do? +

Creates non-sales transaction. 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 non_sales_tender_create_transaction? +

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

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

Can I rate-limit non_sales_tender_create_transaction? +

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

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

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