This record as markdown: /tools/stripe/list-invoices.md
What list_invoices does on Stripe
AI agents call list_invoices 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_invoices is rated Low
This tool retrieves/queries invoice data without creating, modifying, or deleting anything. While it operates in a Financial context (Stripe), the action itself is read-only retrieval. The severity is low because listing invoices is a standard query operation that cannot directly cause financial harm, though the data retrieved could be sensitive and warrant access controls.
From the tool's definition Tool name 'list_invoices' and description 'List all invoices' indicate data retrieval with no modification. The verb 'list' is a classic Read operation pattern.
Attacks that exploit this kind of access
The rule that runs list_invoices 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_invoices, this is the rule to start with:
list_invoices 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_invoices call is checked against it from then on.
Questions about list_invoices
List all invoices. 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_invoices: 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_invoices 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_invoices 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_invoices. 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_invoices 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