Why a prompt is not a cap
Telling the model "never refund more than $50" is a request, not a control. A prompt injection in a customer message, a confused tool call, or a model update can all get past it.
Stripe's refunds.create has no approval step of its own: any key with Refunds: Write can refund any amount.
Put the cap outside the model
Take refund permission away from the agent. Give it one tool, request_refund, that calls a gate holding the key.
The gate reads the real charge from Stripe, checks the amount still refundable, the age, disputes and the customer's earlier refunds, then refunds only if your rules say so.
Route the rest to a person
Above the cap, the gate sends an approve card to the right approver: support lead under $200, finance above. One tap approves, and the refund runs with an idempotency key so it can never go out twice.
Set it up in minutes
Countersign does all of this: paste a restricted key, pick a policy template, give your agent the snippet for its platform.