list_payment_intents

List all PaymentIntents

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-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.

Questions about list_payment_intents

What does the list_payment_intents tool do? +

List all PaymentIntents. 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_payment_intents? +

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.

What risk level is list_payment_intents? +

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

Can I rate-limit list_payment_intents? +

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.

How do I block list_payment_intents completely? +

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.

What MCP server provides list_payment_intents? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Stripe's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.