AI agents use stripe_charges to commit financial operations through UnClick — usually the final step of a payment, billing, or trading workflow. A call moves real money.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | |
action | string | — | list or create (default: list) |
amount | number | — | Amount in smallest currency unit (e.g. cents) |
source | string | — | Payment source or token |
currency | string | — | ISO currency code (e.g. usd) |
customer | string | — | |
secret_key | string | Yes | |
description | string | — | |
starting_after | string | — |
Parameters from the server's own tool schema.
The tool can create Stripe charges, which constitutes committing financial obligations and moving money. Creating a charge bills a customer's payment method, making this a Financial category tool. The 'list' capability is merely Read, but the 'create' capability elevates it to Financial per the most-severe-applicable rule. Misuse could result in unauthorized charges to customers, hence critical severity.
From the tool's definition 'create Stripe charges' — directly initiates financial transactions via Stripe payment processing
Attacks that exploit this kind of access
List or create Stripe charges. It is categorised as a Financial tool in the UnClick MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
stripe_charges accepts 9 parameters: limit, action, amount, source, currency, customer, secret_key, description, starting_after. Required: secret_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for stripe_charges: 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 UnClick. Nothing to install.
stripe_charges 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 stripe_charges 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 stripe_charges. 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.
stripe_charges is provided by the UnClick MCP server (@unclick/mcp-server). 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 →