list_invoices
List the caller's OWN Stripe invoices — status/amounts (minor units)/currency/hosted_invoice_url/period (from stripe_invoices, owner-scoped to the caller's OAuth sub), newest first. Optional limit (default 50, max 200). A billing:view operator may pass all_users:true for the fleet. Returns { coun...
This record as markdown: /tools/dev-busymate-busymate-devtools/list-invoices.md
What list_invoices does on Busymate DevTools
AI agents call list_invoices to retrieve information from Busymate DevTools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max invoices to return (1–200, default 50). |
all_users | boolean | — | billing:view/admin only — return EVERY account's invoices. |
Parameters from the server's own tool schema.
Why list_invoices is rated Low
This tool retrieves financial billing data (invoices) without modifying, deleting, or moving money. It is read-only and scoped to the caller's own data or fleet data for authorized operators. While it exposes financial information, it does not perform financial transactions, create obligations, or execute payments.
From the tool's definition List the caller's OWN Stripe invoices — status/amounts/currency/hosted_invoice_url/period (from stripe_invoices, owner-scoped to the caller's OAuth sub)
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 Busymate DevTools, 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 Busymate DevTools, apply this rule, and every list_invoices call is checked against it from then on.
Questions about list_invoices
List the caller's OWN Stripe invoices — status/amounts (minor units)/currency/hosted_invoice_url/period (from stripe_invoices, owner-scoped to the caller's OAuth sub), newest first. Optional limit (default 50, max 200). A billing:view operator may pass all_users:true for the fleet. Returns { count, invoices:[…] }. It is categorised as a Read tool in the Busymate DevTools MCP Server, which means it retrieves data without modifying state.
list_invoices accepts 2 parameters: limit, all_users. The full parameter table on this page comes from the server's own tool schema.
Register the Busymate DevTools 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 Busymate DevTools. 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 Busymate DevTools MCP server (https://mcp.busymate.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Busymate DevTools, and thousands of servers like it.
This server
Across the catalogue