High Risk →

isw_credit_inquiry

Run Transfer Service credit inquiry before bank credit.

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

AI agents invoke isw_credit_inquiry to trigger processes or run actions in Interswitch. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

isw_credit_inquiry can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-dairus01-interswitch-mcp-server.yaml
tools:
  isw_credit_inquiry:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Interswitch policy for all 74 tools.

Tool Name isw_credit_inquiry
Category Execute
Risk Level High

View all 74 tools →

Agents calling execute-class tools like isw_credit_inquiry 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 Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

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

What does the isw_credit_inquiry tool do? +

Run Transfer Service credit inquiry before bank credit.. It is categorised as a Execute tool in the Interswitch MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on isw_credit_inquiry? +

Add a rule in your Intercept YAML policy under the tools section for isw_credit_inquiry. 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_credit_inquiry? +

isw_credit_inquiry is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit isw_credit_inquiry? +

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

Set action: deny in the Intercept policy for isw_credit_inquiry. 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_credit_inquiry? +

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