stripe_list_invoices
List Stripe invoices
This record as markdown: /tools/io-github-alifanov-scopegate/stripe-list-invoices.md
What stripe_list_invoices does on ScopeGate
AI agents call stripe_list_invoices to retrieve information from ScopeGate without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stripe_list_invoices is rated Low
This tool retrieves (lists) Stripe invoices without modifying or deleting them, placing it in the Read category. While the data retrieved is financially sensitive, the action itself is non-destructive query/retrieval.
From the tool's definition Tool name 'stripe_list_invoices' and description 'List Stripe invoices' indicate retrieval of invoice data without modification. However, invoices are financial records that may contain sensitive payment and customer information.
Attacks that exploit this kind of access
The rule that runs stripe_list_invoices safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stripe_list_invoices, this is the rule to start with:
stripe_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 ScopeGate, apply this rule, and every stripe_list_invoices call is checked against it from then on.
Questions about stripe_list_invoices
List Stripe invoices. It is categorised as a Read tool in the ScopeGate MCP Server, which means it retrieves data without modifying state.
Register the ScopeGate MCP server in PolicyLayer and add a rule for stripe_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 ScopeGate. Nothing to install.
stripe_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 stripe_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 stripe_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.
stripe_list_invoices is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScopeGate, and thousands of servers like it.
This server
Across the catalogue