New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

non_sales_tender_get_transactions

Gets non-sales transactions.

SERVERMCP Dynamics 365 Commerce Server SOURCEjiantmo/mcp-commerce
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/jiantmo-mcp-commerce/non-sales-tender-get-transactions.md

What non_sales_tender_get_transactions does on MCP Dynamics 365 Commerce Server

AI agents call non_sales_tender_get_transactions to retrieve information from MCP Dynamics 365 Commerce Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why non_sales_tender_get_transactions is rated Low

This tool retrieves transaction data without creating, modifying, deleting, or executing operations. The verb 'get' and passive description clearly indicate a read-only data retrieval operation. Even though it accesses financial transaction records, the tool itself performs no financial operations (no money movement or obligation creation), so it is classified as Read rather than Financial.

From the tool's definition Tool name includes 'get_transactions' and description states 'Gets non-sales transactions', indicating a retrieval operation with no modification or deletion of data.

Questions about non_sales_tender_get_transactions

What does the non_sales_tender_get_transactions tool do? +

Gets non-sales transactions. It is categorised as a Read tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on non_sales_tender_get_transactions? +

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

non_sales_tender_get_transactions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit non_sales_tender_get_transactions? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of MCP Dynamics 365 Commerce Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.