Create a refund for a charge
AI agents use create_refund to commit financial operations through Omise MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Refunds move money from the merchant's account back to the customer, constituting a direct financial transaction. This is irreversible and has immediate monetary impact. While not as severe as creating charges or taking payments, refunds are financial operations that could cause significant harm if triggered inappropriately by an AI agent (e.g., refunding the wrong customer or amount).
From the tool's definition Tool name is 'create_refund' and description states 'Create a refund for a charge'. This directly commits a financial obligation—returning money to a customer. The server context confirms it is part of Omise's payment processing API.
Attacks that exploit this kind of access
Create a refund for a charge. It is categorised as a Financial tool in the Omise MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Omise MCP Server MCP server in PolicyLayer and add a rule for create_refund: 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 Omise MCP Server. Nothing to install.
create_refund 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_refund 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_refund. 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_refund is provided by the Omise MCP Server MCP server (jun-omise/omise-mcp-alpha). 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 →