Critical Risk →

high_refund_ratio

Refund ratio ${(ratio * 100).toFixed(0)}%

Part of the Stripe server.

high_refund_ratio can move real money through Stripe, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE STRIPE →

Free to start. No card required.

AI agents use high_refund_ratio to initiate financial transactions through Stripe. Financial operations involve real money and are irreversible once processed. PolicyLayer blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.

high_refund_ratio moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. PolicyLayer blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.

Financial tools involve real money. Block by default and require explicit human approval before enabling.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "high_refund_ratio": {
      "deny_if": [
        {
          "conditions": [],
          "on_deny": "Requires human approval."
        }
      ]
    }
  }
}

See the full Stripe policy for all 39 tools.

Get this rule live on your own Stripe server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY STRIPE →

View all 39 tools →

These attack patterns abuse exactly the kind of access high_refund_ratio gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so high_refund_ratio only ever does what you allow.

SECURE STRIPE →

Other financial tools across the catalogue. The same approach applies to each: deny by default, or require human approval.

What does the high_refund_ratio tool do? +

Refund ratio ${(ratio * 100).toFixed(0)}%. It is categorised as a Financial tool in the Stripe MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on high_refund_ratio? +

Register the Stripe MCP server in PolicyLayer and add a rule for high_refund_ratio: 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 Stripe. Nothing to install.

What risk level is high_refund_ratio? +

high_refund_ratio is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit high_refund_ratio? +

Yes. Add a rate_limit block to the high_refund_ratio 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.

How do I block high_refund_ratio completely? +

Set action: deny in the PolicyLayer policy for high_refund_ratio. 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.

What MCP server provides high_refund_ratio? +

high_refund_ratio is provided by the Stripe MCP server (stripe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Stripe tool call.

Deterministic rules across all 39 Stripe tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.