This record as markdown: /tools/stripe/list-payment-intents.md
What list_payment_intents does on Stripe
AI agents call list_payment_intents 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.
Why list_payment_intents is rated Low
This tool retrieves payment intent records without side effects, placing it in the Read category. However, the severity is medium rather than low because PaymentIntent data can contain sensitive financial information (amounts, customer details, payment status), making unauthorized enumeration a meaningful security concern in a financial system context.
From the tool's definition Tool name 'list_payment_intents' and description 'List all PaymentIntents' indicate a retrieval/query operation. The sibling tools include financial operations (create_refund, create_invoice, cancel_subscription), confirming this is a Stripe payment platform.
Attacks that exploit this kind of access
The rule that runs list_payment_intents 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_payment_intents, this is the rule to start with:
list_payment_intents is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Stripe, apply this rule, and every list_payment_intents call is checked against it from then on.
Questions about list_payment_intents
List all PaymentIntents. It is categorised as a Read tool in the Stripe MCP Server, which means it retrieves data without modifying state.
Register the Stripe MCP server in PolicyLayer and add a rule for list_payment_intents: 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.
list_payment_intents is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_payment_intents 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 list_payment_intents. 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.
list_payment_intents 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.
More on Stripe, and thousands of servers like it.
This server
Across the catalogue