isw_get_pin

Get a card PIN. Sensitive operation; requires confirm: true and redacts sensitive fields.

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

WHAT IT DOES

What isw_get_pin does on Interswitch

AI agents call isw_get_pin 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_pin is rated Low

The primary function is data retrieval ('Get'), which maps to the Read category. Severity is elevated to 'medium' rather than 'low' because: (1) PIN data is cryptographically sensitive and could enable unauthorized card transactions if disclosed; (2) the tool explicitly requires a confirmation flag ('confirm: true'), suggesting the system treats this as a guarded operation; (3) misuse by an AI agent could expose…

From the tool's definition Tool name 'isw_get_pin' and description 'Get a card PIN' indicate a retrieval operation. Description explicitly states it 'Get[s]' data (Read verb).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

isw_get_pin Allowed

isw_get_pin 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_pin": {}
  }
}

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

FAQ

Questions about isw_get_pin

What does the isw_get_pin tool do? +

Get a card PIN. Sensitive operation; requires confirm: true and redacts sensitive fields. 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_pin? +

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

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

Can I rate-limit isw_get_pin? +

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

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

isw_get_pin 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_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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