listPaymentMethods
List saved payment methods for an organisation. Returns masked card metadata only (brand, last4, exp month/year, default flag). NEVER returns full card numbers, CVCs, or any Stripe IDs.
This record as markdown: /tools/io-stablebaseline-sb/listpaymentmethods.md
What listPaymentMethods does on Stable Baseline
AI agents call listPaymentMethods to retrieve information from Stable Baseline without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
organisation_id | string | Yes | UUID of the organisation. Must match the credential's organisation. |
Parameters from the server's own tool schema.
Why listPaymentMethods is rated Low
This tool retrieves payment method metadata without side effects. Although it accesses financial information (payment methods), it does not move money, create charges, refund funds, or modify subscriptions—therefore it is Read rather than Financial. The masking of sensitive fields (no full card numbers or CVCs) further limits the practical risk.
From the tool's definition Tool name 'listPaymentMethods' and description 'List saved payment methods' indicate a retrieval operation. Description explicitly states it 'Returns masked card metadata only (brand, last4, exp month/year, default flag).
Attacks that exploit this kind of access
The rule that runs listPaymentMethods safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stable Baseline, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For listPaymentMethods, this is the rule to start with:
listPaymentMethods 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 Stable Baseline, apply this rule, and every listPaymentMethods call is checked against it from then on.
Questions about listPaymentMethods
List saved payment methods for an organisation. Returns masked card metadata only (brand, last4, exp month/year, default flag). NEVER returns full card numbers, CVCs, or any Stripe IDs. It is categorised as a Read tool in the Stable Baseline MCP Server, which means it retrieves data without modifying state.
listPaymentMethods accepts 1 parameter: organisation_id. Required: organisation_id. The full parameter table on this page comes from the server's own tool schema.
Register the Stable Baseline MCP server in PolicyLayer and add a rule for listPaymentMethods: 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 Stable Baseline. Nothing to install.
listPaymentMethods 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 listPaymentMethods 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 listPaymentMethods. 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.
listPaymentMethods is provided by the Stable Baseline MCP server (https://api.stablebaseline.io/functions/v1/cloud-serve/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stable Baseline, and thousands of servers like it.
This server
Across the catalogue