stripe_list_subscriptions
A read tool on the Integrations MCP server.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/stripe-list-subscriptions.md
What stripe_list_subscriptions does on Integrations MCP
AI agents call stripe_list_subscriptions to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stripe_list_subscriptions is rated Low
This tool queries subscription data from Stripe, which is a read-only operation that retrieves existing information without side effects. However, severity is elevated to medium rather than low because subscription data may contain sensitive billing and customer information that could be misused if exposed to an untrusted agent (e.g., leaking customer lists or billing details).
From the tool's definition Tool name is 'stripe_list_subscriptions' which retrieves subscription data. The 'list' action and subscriptions context indicate a query operation with no modification capability.
Attacks that exploit this kind of access
The rule that runs stripe_list_subscriptions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stripe_list_subscriptions, this is the rule to start with:
stripe_list_subscriptions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every stripe_list_subscriptions call is checked against it from then on.
Questions about stripe_list_subscriptions
stripe_list_subscriptions is a read tool on the Integrations MCP server. 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_subscriptions: 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_subscriptions 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_subscriptions 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_subscriptions. 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_subscriptions 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.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue