Create a transaction for an order (e.g. capture, sale, refund). Side effect: creates a Transaction record and may change order financial_status. kind: authorization | capture | sale | void | refund.
AI agents use create_order_transaction to commit financial operations through Sapo — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool creates financial transaction records and can trigger money movement (capture, sale, refund, void). It directly affects the financial status of orders and involves real monetary operations, making it Financial category with critical severity due to potential for fraudulent refunds, unauthorized captures, or voiding legitimate payments.
From the tool's definition 'Create a transaction for an order (e.g. capture, sale, refund)' and 'kind: authorization | capture | sale | void | refund' — directly creates financial transactions including refunds, captures, and sales
Documented attack patterns abuse exactly the kind of access create_order_transaction 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 create_order_transaction:
{
"version": "1",
"default": "deny",
"tools": {
"create_order_transaction": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to create_order_transaction is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Create a transaction for an order (e.g. capture, sale, refund). Side effect: creates a Transaction record and may change order financial_status. kind: authorization | capture | sale | void | refund. It is categorised as a Financial tool in the Sapo MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Sapo MCP server in PolicyLayer and add a rule for create_order_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 Sapo. Nothing to install.
create_order_transaction is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the create_order_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 create_order_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.
create_order_transaction 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.