AI agents use stripe_customers to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | — | |
email | string | — | |
limit | number | — | |
phone | string | — | |
action | string | — | list or create (default: list) |
secret_key | string | Yes | Stripe secret key (sk_live_* or sk_test_*) |
description | string | — | |
starting_after | string | — | Pagination cursor (customer ID) |
Parameters from the server's own tool schema.
Creating Stripe customers is a reversible Write operation that establishes new financial entities in the Stripe system. While not directly moving money (which would be Financial), it creates customer records that are prerequisites for financial transactions. An AI agent misusing this could create fraudulent customer accounts or spam the system, justifying high severity.
From the tool's definition Tool description states 'List or create Stripe customers.' The create operation modifies Stripe's customer database, making this a Write action. Listing is Read, but the tool's primary documented capability includes creation.
Attacks that exploit this kind of access
List or create Stripe customers. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
stripe_customers accepts 8 parameters: name, email, limit, phone, action, 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_customers: 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_customers is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the stripe_customers 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_customers. 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_customers 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 →