isw_block_card

Block a card immediately. Requires confirm: true.

SERVERInterswitch SOURCEinterswitch-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What isw_block_card does on Interswitch

AI agents call isw_block_card to permanently remove resources in Interswitch, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why isw_block_card is rated Critical

Blocking a card immediately disables a user's ability to make payments, which is a severe, difficult-to-reverse financial operation. It falls under Destructive because it irreversibly (or near-irreversibly) disables a financial asset. The blast radius is critical — misuse could lock a legitimate cardholder out of their funds.

From the tool's definition 'Block a card immediately' — blocking a card is an irreversible or hard-to-reverse action that disables a financial instrument, with immediate effect. 'Requires confirm: true' further signals the destructive/high-impact nature.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs isw_block_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_block_card, this is the rule to start with:

isw_block_card Hidden

isw_block_card is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "isw_block_card"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Interswitch, apply this rule, and every isw_block_card call is checked against it from then on.

FAQ

Questions about isw_block_card

What does the isw_block_card tool do? +

Block a card immediately. Requires confirm: true. It is categorised as a Destructive tool in the Interswitch MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on isw_block_card? +

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

What risk level is isw_block_card? +

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

Can I rate-limit isw_block_card? +

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

How do I block isw_block_card completely? +

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

What MCP server provides isw_block_card? +

isw_block_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.

KEEP EXPLORING

More on Interswitch, and thousands of servers like it.

This server

All 74 Interswitch tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →