List payments from GoCardless
AI agents call list_payments to retrieve information from GoCardless MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves payment data from GoCardless without creating, modifying, deleting, or executing external operations. While the data retrieved may be financially sensitive (payment information), the tool itself performs only a read operation. Severity is low because listing existing payments poses minimal risk—the data already exists and is not altered.
From the tool's definition Tool name 'list_payments' and description 'List payments from GoCardless' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List payments from GoCardless. It is categorised as a Read tool in the GoCardless MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GoCardless MCP Server MCP server in PolicyLayer and add a rule for list_payments: 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 GoCardless MCP Server. Nothing to install.
list_payments 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 list_payments 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 list_payments. 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.
list_payments is provided by the GoCardless MCP Server MCP server (jmceleney/gocardless-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 →