isw_get_transaction_details

Get Transaction Search details by transactionId.

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-details.md

WHAT IT DOES

What isw_get_transaction_details does on Interswitch

AI agents call isw_get_transaction_details 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.

RISK

Why isw_get_transaction_details is rated Low

This tool retrieves/queries existing transaction data based on a transaction ID. It performs no modification, execution of code, deletion, or financial operations. It is a straightforward read-only lookup operation, typical of transaction history or reconciliation queries in payment systems.

From the tool's definition Tool name 'isw_get_transaction_details' and description 'Get Transaction Search details by transactionId' indicate a retrieval operation with no mutation or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

isw_get_transaction_details Allowed

isw_get_transaction_details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "isw_get_transaction_details": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about isw_get_transaction_details

What does the isw_get_transaction_details tool do? +

Get Transaction Search details by transactionId. 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_details? +

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

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

Can I rate-limit isw_get_transaction_details? +

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

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

isw_get_transaction_details 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 →

Across the catalogue

get_event_details on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →