refund_stripe_charge
Refund a Stripe charge (ch_… or a pi_… payment intent): the full refundable amount, or a partial
This record as markdown: /tools/hermoso/refund-stripe-charge.md
What refund_stripe_charge does on Hermoso
AI agents use refund_stripe_charge to commit financial operations through Hermoso, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why refund_stripe_charge is rated Critical
refund_stripe_charge moves real money, and an autonomous agent will call it with the same confidence it calls a search tool. A misread instruction or an injected prompt is all it takes to drain an account or blow a budget.
Attacks that exploit this kind of access
The rule that runs refund_stripe_charge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hermoso, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For refund_stripe_charge, this is the rule to start with:
Any call to refund_stripe_charge is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Hermoso, apply this rule, and every refund_stripe_charge call is checked against it from then on.
Questions about refund_stripe_charge
Refund a Stripe charge (ch_… or a pi_… payment intent): the full refundable amount, or a partial. It is categorised as a Financial tool in the Hermoso MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Hermoso MCP server in PolicyLayer and add a rule for refund_stripe_charge: 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 Hermoso. Nothing to install.
refund_stripe_charge 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_stripe_charge 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_stripe_charge. 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_stripe_charge is provided by the Hermoso MCP server (https://app.hermoso.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hermoso, and thousands of servers like it.
Across the catalogue