isw_create_card
Provision a new Verve card through Card 360. Requires confirm: true.
This record as markdown: /tools/io-github-dairus01-interswitch-mcp-server/isw-create-card.md
What isw_create_card does on Interswitch
AI agents use isw_create_card to commit financial operations through Interswitch, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why isw_create_card is rated Critical
Provisioning a new payment card is a financial operation that creates a new financial instrument, likely incurring costs or committing financial obligations on behalf of the organization or customer. This falls under Financial as it directly relates to payment card issuance, which is a regulated financial activity with significant blast radius if misused by an AI agent.
From the tool's definition Provision a new Verve card through Card 360
Attacks that exploit this kind of access
The rule that runs isw_create_card safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Interswitch, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For isw_create_card, this is the rule to start with:
Any call to isw_create_card is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Interswitch, apply this rule, and every isw_create_card call is checked against it from then on.
Questions about isw_create_card
Provision a new Verve card through Card 360. Requires confirm: true. 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.
Register the Interswitch MCP server in PolicyLayer and add a rule for isw_create_card: 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.
isw_create_card 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 isw_create_card 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 isw_create_card. 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.
isw_create_card 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.
Across the catalogue