non_sales_tender_create_transaction
Creates non-sales transaction.
This record as markdown: /tools/jiantmo-mcp-commerce/non-sales-tender-create-transaction.md
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 non_sales_tender_create_transaction is rated Medium
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
The rule that runs non_sales_tender_create_transaction safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Dynamics 365 Commerce Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For non_sales_tender_create_transaction, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Dynamics 365 Commerce Server, apply this rule, and every non_sales_tender_create_transaction call is checked against it from then on.
Questions about non_sales_tender_create_transaction
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.
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.
non_sales_tender_create_transaction is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
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.
More on MCP Dynamics 365 Commerce Server, and thousands of servers like it.
This server
Across the catalogue