List normalized payout records with optional filtering and pagination.
AI agents call list_payouts to retrieve information from Stripe Reporting without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves payout records from Stripe without modifying, deleting, or executing any actions. It fits the Read category definition: 'retrieves or queries data; no side effects'. The read-only nature of the server and the non-mutating behavior of listing operations confirm low severity.
From the tool's definition Server explicitly described as 'Read-only Stripe finance, ops, and risk reporting' and 'without mutating Stripe state'. Tool name 'list_payouts' indicates retrieval/query operation.
Attacks that exploit this kind of access
List normalized payout records with optional filtering and pagination. It is categorised as a Read tool in the Stripe Reporting MCP Server, which means it retrieves data without modifying state.
Register the Stripe Reporting MCP server in PolicyLayer and add a rule for list_payouts: 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 Reporting. Nothing to install.
list_payouts 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_payouts 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_payouts. 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_payouts is provided by the Stripe Reporting MCP server (ohrytskov/stripe-reporting-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →