Retrieve card payment accept result
AI agents call cart_retrieve_card_payment_accept_result to retrieve information from MCP Dynamics 365 Commerce Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns the result of a card payment acceptance operation. It has no side effects: it does not create, modify, delete, or execute any action. The retrieval of payment results is a read-only operation that presents historical or status data about an already-completed payment transaction.
From the tool's definition Tool name contains 'retrieve' and description states 'Retrieve card payment accept result' — both indicate data retrieval with no modification or deletion of records.
Attacks that exploit this kind of access
Retrieve card payment accept result. 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_retrieve_card_payment_accept_result: 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_retrieve_card_payment_accept_result 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_retrieve_card_payment_accept_result 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_retrieve_card_payment_accept_result. 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_retrieve_card_payment_accept_result 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →