create_refund
AI agents use create_refund to commit financial operations through Green Helix — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Refunds are irreversible financial transactions that commit monetary obligations and transfer funds. Even though the description is empty, the server context (AI agent commerce platform with payment tools) and tool name leave no ambiguity. Misuse by an AI agent could result in unauthorized refunds, financial loss, and fraud. This is the most severe category.
From the tool's definition Tool name 'create_refund' in a commerce platform context (sibling tools include create_payment_intent, create_subscription, list_charges, list_invoices) indicates direct manipulation of financial transactions. Refunds move money back to customers.
Attacks that exploit this kind of access
create_refund. It is categorised as a Financial tool in the Green Helix MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Green Helix 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 Green Helix. 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 Green Helix MCP server (mirni/a2a). 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 →