isw_requery_transfer

Requery Transfer Service transaction status.

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-requery-transfer.md

WHAT IT DOES

What isw_requery_transfer does on Interswitch

AI agents call isw_requery_transfer 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_requery_transfer is rated Low

The tool queries the status of an existing transfer transaction. 'Requery' is a read/lookup operation that retrieves transaction status without initiating, modifying, or deleting any financial transaction. No side effects are implied.

From the tool's definition Requery Transfer Service transaction status

Attacks that exploit this kind of access

RECOMMENDED RULE

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

isw_requery_transfer Allowed

isw_requery_transfer 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_requery_transfer": {}
  }
}

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_requery_transfer call is checked against it from then on.

FAQ

Questions about isw_requery_transfer

What does the isw_requery_transfer tool do? +

Requery Transfer Service transaction status. 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_requery_transfer? +

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

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

Can I rate-limit isw_requery_transfer? +

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

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

isw_requery_transfer 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

The MCP Attack Database →

Guides

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