Create a new payment in GoCardless
AI agents use create_payment to commit financial operations through GoCardless MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly creates payment transactions within a financial system (GoCardless). Misuse by an AI agent could result in unauthorized charges, fraudulent payments, or financial loss. This is a critical financial operation that irreversibly commits funds, placing it in the Financial category with critical severity.
From the tool's definition Tool name 'create_payment' combined with server description stating it 'manages customers, payments, mandates, subscriptions, and payouts' explicitly indicates creation of financial transactions.
Attacks that exploit this kind of access
Create a new payment in GoCardless. It is categorised as a Financial tool in the GoCardless MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the GoCardless MCP Server MCP server in PolicyLayer and add a rule for create_payment: 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.
create_payment is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the create_payment 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 create_payment. 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.
create_payment 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 →