list_setup_intents

List all SetupIntents

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-setup-intents.md

WHAT IT DOES

What list_setup_intents does on Stripe

AI agents call list_setup_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.

RISK

Why list_setup_intents is rated Low

This is a read-only operation that queries and retrieves SetupIntent data from Stripe. SetupIntents are payment authorization records used for future charges. Listing them has no side effects, does not modify data, and does not move money. The blast radius is minimal—an agent could view payment setup details but cannot charge, delete, or alter them. Classified as Read with low severity.

From the tool's definition Tool name 'list_setup_intents' and description 'List all SetupIntents' indicate retrieval of existing Stripe SetupIntent records without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_setup_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_setup_intents, this is the rule to start with:

list_setup_intents Allowed

list_setup_intents 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_setup_intents": {}
  }
}

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_setup_intents call is checked against it from then on.

FAQ

Questions about list_setup_intents

What does the list_setup_intents tool do? +

List all SetupIntents. 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_setup_intents? +

Register the Stripe MCP server in PolicyLayer and add a rule for list_setup_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_setup_intents? +

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

Can I rate-limit list_setup_intents? +

Yes. Add a rate_limit block to the list_setup_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_setup_intents completely? +

Set action: deny in the PolicyLayer policy for list_setup_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_setup_intents? +

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

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 →