List payouts from GoCardless
AI agents call list_payouts 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 returns payout data without modifying, deleting, or executing operations. It is a read-only retrieval operation similar to sibling tools like 'list_customers', 'list_mandates', and 'list_payments'. Even though it accesses financial data, the tool itself does not move money or commit financial obligations—it only retrieves existing payout information.
From the tool's definition Tool name 'list_payouts' and description 'List payouts from GoCardless' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List payouts 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_payouts: 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_payouts 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_payouts 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_payouts. 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_payouts 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 →