isw_bulk_transfer

Send money to multiple bank accounts. High-risk financial operation; requires confirm: true. Max 100 transactions.

SERVERInterswitch SOURCEinterswitch-mcp-server
Critical RISK CLASS
Category Financial
Parameters 00 required
Recommended Approval-gatedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dairus01-interswitch-mcp-server/isw-bulk-transfer.md

What isw_bulk_transfer does on Interswitch

AI agents use isw_bulk_transfer to commit financial operations through Interswitch, usually the final step of a payment, billing, or trading workflow. A call moves real money.

Why isw_bulk_transfer is rated Critical

This tool moves money (transfers) to multiple recipients, committing financial obligations. It is irreversible and has direct monetary impact. Even with the confirm flag requirement, bulk transfers represent the highest severity category. The ability to transfer to up to 100 accounts in one operation amplifies blast radius if an AI agent is tricked into misuse.

From the tool's definition Tool explicitly described as 'Send money to multiple bank accounts' and flagged as 'High-risk financial operation.' Context confirms this is part of Interswitch payment/transfer APIs.

Questions about isw_bulk_transfer

What does the isw_bulk_transfer tool do? +

Send money to multiple bank accounts. High-risk financial operation; requires confirm: true. Max 100 transactions. It is categorised as a Financial tool in the Interswitch MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on isw_bulk_transfer? +

Register the Interswitch MCP server in PolicyLayer and add a rule for isw_bulk_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 Interswitch. Nothing to install.

What risk level is isw_bulk_transfer? +

isw_bulk_transfer is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit isw_bulk_transfer? +

Yes. Add a rate_limit block to the isw_bulk_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.

How do I block isw_bulk_transfer completely? +

Set action: deny in the PolicyLayer policy for isw_bulk_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.

What MCP server provides isw_bulk_transfer? +

isw_bulk_transfer is provided by the Interswitch MCP server (interswitch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Interswitch, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Interswitch's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.