List all transactions for a specific order. Returns payment attempts, captures, refunds, and voids linked to the order.
AI agents call list_order_transactions to retrieve information from Sapo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical transaction data associated with an order. It performs a read-only operation that does not create, modify, delete, or execute any actions. While it accesses financial transaction records, it does not move money or commit financial obligations—it merely retrieves information about past transactions. Therefore, it falls into the Read category with low severity.
From the tool's definition Tool name 'list_order_transactions' and description states it 'List[s] all transactions for a specific order' and 'Returns payment attempts, captures, refunds, and voids linked to the order.' The verb 'list' and 'returns' indicate data retrieval with no…
Documented attack patterns abuse exactly the kind of access list_order_transactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sapo, and nothing reaches the server without passing your rules. This is the rule we recommend for list_order_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"list_order_transactions": {}
}
}list_order_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all transactions for a specific order. Returns payment attempts, captures, refunds, and voids linked to the order. It is categorised as a Read tool in the Sapo MCP Server, which means it retrieves data without modifying state.
Register the Sapo MCP server in PolicyLayer and add a rule for list_order_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 Sapo. Nothing to install.
list_order_transactions 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 list_order_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.
Set action: deny in the PolicyLayer policy for list_order_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.
list_order_transactions is provided by the Sapo MCP server (nguyennguyenit/sapo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Sapo, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
93 Sapo tools catalogued and risk-classified — across an index of 43,000+ MCP servers.