Critical Risk →

isw_requery_transfer

Requery Transfer Service transaction status.

Part of the Interswitch MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use isw_requery_transfer to initiate financial transactions through Interswitch. Financial operations involve real money and are irreversible once processed. Intercept blocks financial tools by default, requiring explicit human approval with transaction-level limits to prevent unauthorised spending.

isw_requery_transfer moves real money. Without a policy, an autonomous agent could initiate transactions that drain accounts or exceed budgets. Intercept blocks financial tools by default, requiring human-in-the-loop approval with configurable spending limits per transaction and per time window.

Financial tools involve real money. Block by default and require explicit human approval before enabling.

io-github-dairus01-interswitch-mcp-server.yaml
tools:
  isw_requery_transfer:
    rules:
      - action: deny
        reason: "Requires human approval"

See the full Interswitch policy for all 74 tools.

Tool Name isw_requery_transfer
Category Financial
Risk Level Critical

View all 74 tools →

Agents calling financial-class tools like isw_requery_transfer have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Financial risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

isw_requery_transfer is one of the critical-risk operations in Interswitch. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the isw_requery_transfer tool do? +

Requery Transfer Service transaction status.. It is categorised as a Financial tool in the Interswitch MCP Server, which means it involves financial transactions. Block by default and require explicit approval.

How do I enforce a policy on isw_requery_transfer? +

Add a rule in your Intercept YAML policy under the tools section for isw_requery_transfer. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Interswitch MCP server.

What risk level is isw_requery_transfer? +

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

Can I rate-limit isw_requery_transfer? +

Yes. Add a rate_limit block to the isw_requery_transfer rule in your Intercept 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 Intercept 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). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.