Return current available and pending balances grouped by currency.
AI agents call get_balance_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 balance information from Stripe without creating, modifying, deleting, or executing any operations. It has no side effects and poses minimal risk even if called by an AI agent, as it only exposes existing financial visibility data. The read-only nature of the server and the retrieval-only semantics of this specific tool place it firmly in the Read category with low severity.
From the tool's definition Tool name 'get_balance_summary' and description 'Return current available and pending balances grouped by currency' indicate a query operation that retrieves financial data without mutation.
Attacks that exploit this kind of access
Return current available and pending balances grouped by currency. 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_balance_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_balance_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_balance_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_balance_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_balance_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 →