Return gross, refund, and net revenue totals for a time window.
AI agents call get_revenue_summary 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 historical revenue data within a specified time window. It has no side effects, performs no state mutations, and poses minimal risk if misused by an AI agent—the worst outcome would be reading financial metrics the agent shouldn't access. This is a pure data retrieval operation consistent with the Read category.
From the tool's definition Tool name 'get_revenue_summary' and description 'Return gross, refund, and net revenue totals for a time window' indicate a query operation with no data mutation. Server description explicitly states 'Read-only' and 'without mutating Stripe state'.
Attacks that exploit this kind of access
Return gross, refund, and net revenue totals for a time window. 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_revenue_summary: 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_revenue_summary 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_revenue_summary 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_revenue_summary. 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_revenue_summary 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 →