isw_get_transaction_status

Get Quickteller transaction status by transactionRef.

SERVERInterswitch SOURCEinterswitch-mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dairus01-interswitch-mcp-server/isw-get-transaction-status.md

What isw_get_transaction_status does on Interswitch

AI agents call isw_get_transaction_status 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_get_transaction_status is rated Low

This tool queries and retrieves the status of an existing transaction using a reference ID. It has no side effects, does not create, modify, or delete data, and does not execute external operations or move funds. It is a straightforward read operation on financial transaction metadata.

From the tool's definition Get Quickteller transaction status by transactionRef - uses 'Get' verb and retrieves transaction status without modifying data or triggering operations.

Questions about isw_get_transaction_status

What does the isw_get_transaction_status tool do? +

Get Quickteller transaction status by transactionRef. It is categorised as a Read tool in the Interswitch MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on isw_get_transaction_status? +

Register the Interswitch MCP server in PolicyLayer and add a rule for isw_get_transaction_status: 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_get_transaction_status? +

isw_get_transaction_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit isw_get_transaction_status? +

Yes. Add a rate_limit block to the isw_get_transaction_status 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_get_transaction_status completely? +

Set action: deny in the PolicyLayer policy for isw_get_transaction_status. 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_get_transaction_status? +

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