stripe_list_charges
AI agents call stripe_list_charges to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries charge records from Stripe—a read-only operation with no side effects on data. However, it accesses sensitive financial transaction information which could expose payment details, customer data, or transaction history if misused by an agent without proper authorization controls.
From the tool's definition Tool name 'stripe_list_charges' indicates a retrieval operation ('list') against Stripe's charges endpoint. The empty description prevents full certainty, but the naming convention aligns with querying financial transaction data without modification.
Attacks that exploit this kind of access
stripe_list_charges. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for stripe_list_charges: 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 Integrations MCP. Nothing to install.
stripe_list_charges 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 stripe_list_charges 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 stripe_list_charges. 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.
stripe_list_charges is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →