Return payment, refund, fee, and payout totals for reconciliation.
AI agents call get_reconciliation_report 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 financial reconciliation summaries without modifying any state. It falls squarely into the Read category—querying and retrieving data for reporting purposes. Severity is low because the blast radius of misuse is limited to information disclosure; no financial transactions, deletions, or code execution are possible.
From the tool's definition Tool description states it 'Return[s]' reconciliation data (payment, refund, fee, and payout totals). Server description explicitly states 'Read-only' and 'without mutating Stripe state'. Tool name and description indicate data retrieval only.
Attacks that exploit this kind of access
Return payment, refund, fee, and payout totals for reconciliation. 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 get_reconciliation_report: 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.
get_reconciliation_report 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 get_reconciliation_report 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 get_reconciliation_report. 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.
get_reconciliation_report 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 →