This record as markdown: /tools/io-github-dairus01-interswitch-mcp-server/isw-check-debit-balance.md
What isw_check_debit_balance does on Interswitch
AI agents call isw_check_debit_balance to retrieve information from Interswitch without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why isw_check_debit_balance is rated Low
This tool performs a read-only operation—querying the balance of a debit card account. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions or irreversible actions.
From the tool's definition Tool name 'isw_check_debit_balance' and description 'Check debit card balance' indicate a query operation that retrieves balance information without modifying or affecting any data.
Attacks that exploit this kind of access
The rule that runs isw_check_debit_balance 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_check_debit_balance, this is the rule to start with:
isw_check_debit_balance is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Interswitch, apply this rule, and every isw_check_debit_balance call is checked against it from then on.
Questions about isw_check_debit_balance
Check debit card balance. It is categorised as a Read tool in the Interswitch MCP Server, which means it retrieves data without modifying state.
Register the Interswitch MCP server in PolicyLayer and add a rule for isw_check_debit_balance: 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_check_debit_balance is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the isw_check_debit_balance 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_check_debit_balance. 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_check_debit_balance 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.
This server
Across the catalogue