list_customers

List all customers

SERVERStripe SOURCE@modelcontextprotocol/server-stripe

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/stripe/list-customers.md

WHAT IT DOES

What list_customers does on Stripe

AI agents call list_customers to retrieve information from Stripe without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_customers is rated Low

This tool retrieves and enumerates customer data without creating, modifying, or deleting anything. It is a read-only query operation. Severity is low because listing customers is informational and carries minimal risk; the blast radius of misuse is limited to data exposure rather than financial or destructive harm.

From the tool's definition Tool name 'list_customers' and description 'List all customers' indicate a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_customers safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Stripe, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_customers, this is the rule to start with:

list_customers Allowed

list_customers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_customers": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Stripe, apply this rule, and every list_customers call is checked against it from then on.

FAQ

Questions about list_customers

What does the list_customers tool do? +

List all customers. It is categorised as a Read tool in the Stripe MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_customers? +

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

What risk level is list_customers? +

list_customers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_customers? +

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

How do I block list_customers completely? +

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

What MCP server provides list_customers? +

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

KEEP EXPLORING

More on Stripe, and thousands of servers like it.

This server

All 27 Stripe tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →