// SCAN REPORT

Stripe Reporting

14 tools. 3 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 2 Jul 2026

3 can modify or destroy data

11 read-only

14 tools total

Community server · catalogue entry verified 02/07/2026

How to control Stripe Reporting ↓

TOOL MAP

What Stripe Reporting exposes to your agents

Read (11) Write / Execute (2) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Stripe Reporting tools

Destructive · Critical delete Despite the server being described as 'read-only' and not mutating Stripe state, this tool's name and description explicitly indicate it deletes documents. Write · Medium create_collection This tool creates a new collection (a persistent data structure), which is a reversible write operation. Write · High save The tool creates or modifies data in MongoDB collections persistently (e.g., flagged entities, notes, pinned reports, saved cohorts).

3 of Stripe Reporting's 14 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Stripe Reporting

PolicyLayer is an MCP gateway — it sits between your AI agents and Stripe Reporting, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_collection": {
    "limits": [
      {
        "counter": "create_collection_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "find": {
    "limits": [
      {
        "counter": "find_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Stripe Reporting — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON STRIPE REPORTING →

Instant setup, no code required.

FULL CATALOGUE

All 14 Stripe Reporting tools

DESTRUCTIVE 1 tools

Destructive delete Delete documents matching a filter. Empty filters are rejected — pass at least one field.

WRITE 2 tools

Write create_collection Explicitly create a new collection. save() also creates collections on first use; this is for when you want an Write save Save a document to a Mongo collection. Creates the collection on first write. Use for flagged entities, notes,

READ 11 tools

Read find Query documents in a user collection. Returns up to 50 by default, 1000 max. Read get_balance_summary Return current available and pending balances grouped by currency. Read get_customer_payments Return a customer summary and the customer payment history. Read get_payment Return the normalized details for a single payment, including refunds and disputes. Read get_reconciliation_report Return payment, refund, fee, and payout totals for reconciliation. Read get_revenue_summary Return gross, refund, and net revenue totals for a time window. Read get_risk_alerts Return derived finance and payment risk alerts for the selected time window. Read list_collections List user-writable collections with the document count belonging to the current user. Read list_customers List normalized customer records with derived payment summaries. Read list_payments List normalized payment records with optional filtering and pagination. Read list_payouts List normalized payout records with optional filtering and pagination.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Stripe Reporting

Can an AI agent delete data through the Stripe Reporting MCP server? +

Yes. The Stripe Reporting server exposes 1 destructive tools including delete. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Stripe Reporting? +

The Stripe Reporting server has 2 write tools including create_collection, save. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Stripe Reporting.

How many tools does the Stripe Reporting MCP server expose? +

14 tools across 3 categories: Destructive, Read, Write. 11 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Stripe Reporting? +

Register the Stripe Reporting MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Stripe Reporting tool call.

Deterministic rules across all 14 Stripe Reporting tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON STRIPE REPORTING →

Instant setup, no code required.

14 Stripe Reporting tools catalogued and risk-classified — across an index of 43,000+ MCP servers.