What it does
This rule sets Claude Code to ask for confirmation before it runs Stripe MCP tools that write data, move money or start a Stripe Atlas company formation. Read and documentation tools run without a prompt.
It suits users who connect Stripe through MCP and want a client-side approval step on changes. The publisher notes that Stripe's own MCP documentation recommends this kind of approval, because Stripe itself confirms only some writes, such as refunds and outbound payments.
The rule applies only to an MCP server named 'stripe', such as the name used by the Stripe devtools setup. If the server has any other name, no prompts are shown.
Limitations and requirements
Applies only to an MCP server named 'stripe'; under any other name nothing is prompted. Stripe itself confirms only some writes (refunds and outbound payments), so the approval prompts are a client-side step.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 17 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 30
stripe-mcp-confirm-writes
Ask before Claude runs a Stripe MCP tool that writes data, moves money or starts a Stripe Atlas company formation; read and docs tools still run freely. Stripe's MCP docs recommend client-side tool approval, since Stripe itself only confirms some writes (refunds, outbound payments). Only covers a server named 'stripe' (as installed by --mcp devtools/stripe); under any other name nothing is prompted.
As shown on www.aitmpl.com when we last read it