cart_get_payments_history
Get payments history
This record as markdown: /tools/jiantmo-mcp-commerce/cart-get-payments-history.md
What cart_get_payments_history does on MCP Dynamics 365 Commerce Server
AI agents call cart_get_payments_history 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 cart_get_payments_history is rated Low
This tool retrieves historical payment information from a shopping cart context. It performs a read-only query operation that returns existing data without any side effects, modifications, deletions, or financial transactions. While payment data is sensitive, the tool itself only reads/retrieves it rather than executing transactions or making changes.
From the tool's definition Tool name 'cart_get_payments_history' uses the 'get' verb and description states 'Get payments history', indicating a retrieval operation with no modification of data.
Attacks that exploit this kind of access
The rule that runs cart_get_payments_history 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 cart_get_payments_history, this is the rule to start with:
cart_get_payments_history is read-only, so it stays allowed. 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 cart_get_payments_history call is checked against it from then on.
Questions about cart_get_payments_history
Get payments history. It is categorised as a Read tool in the MCP Dynamics 365 Commerce Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Dynamics 365 Commerce Server MCP server in PolicyLayer and add a rule for cart_get_payments_history: 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.
cart_get_payments_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cart_get_payments_history 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 cart_get_payments_history. 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.
cart_get_payments_history 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