Process refund for a completed order
AI agents use refund_order to commit financial operations through Satim Payment Gateway Integration — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Refunds are irreversible financial operations that directly move money back to customer accounts. Any misuse by an AI agent (refunding orders without authorization, refunding arbitrary amounts, or systematic refund abuse) could cause direct financial loss to the merchant. This is the highest-severity category and the most critical use case for access control.
From the tool's definition Tool name 'refund_order' combined with description 'Process refund for a completed order' on a payment gateway server explicitly handles reversal of financial transactions.
Documented attack patterns abuse exactly the kind of access refund_order gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Satim Payment Gateway Integration, and nothing reaches the server without passing your rules. This is the rule we recommend for refund_order:
{
"version": "1",
"default": "deny",
"tools": {
"refund_order": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to refund_order is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Process refund for a completed order. It is categorised as a Financial tool in the Satim Payment Gateway Integration MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Satim Payment Gateway Integration MCP server in PolicyLayer and add a rule for refund_order: 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 Satim Payment Gateway Integration. Nothing to install.
refund_order 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 refund_order 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 refund_order. 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.
refund_order is provided by the Satim Payment Gateway Integration MCP server (zakblacki/satim-payment-gateway-integration). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Satim Payment Gateway Integration, 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.
5 Satim Payment Gateway Integration tools catalogued and risk-classified — across an index of 43,000+ MCP servers.