Create a bank transfer
AI agents use create_transfer to commit financial operations through Nomba MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Bank transfers move money and commit financial obligations. This is the most severe category (Financial > Destructive > Execute > Write > Read). The tool's primary purpose is to execute financial transactions that alter account balances and represent real monetary movement, making misuse by an AI agent potentially catastrophic.
From the tool's definition Tool name 'create_transfer' and description 'Create a bank transfer' combined with server context stating it 'allows users to manage transactions, bank transfers, virtual accounts, and POS terminals via the Nomba API' in a payment platform.
Attacks that exploit this kind of access
Create a bank transfer. It is categorised as a Financial tool in the Nomba MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Nomba MCP Server MCP server in PolicyLayer and add a rule for create_transfer: 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 Nomba MCP Server. Nothing to install.
create_transfer 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_transfer 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_transfer. 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_transfer is provided by the Nomba MCP Server MCP server (theyahia/nomba-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 →