isw_reissue_card_pin
Reissue a Card 360 card PIN. The plaintext pin is encrypted locally and never sent. Requires confirm: true.
This record as markdown: /tools/io-github-dairus01-interswitch-mcp-server/isw-reissue-card-pin.md
What isw_reissue_card_pin does on Interswitch
AI agents use isw_reissue_card_pin to create or update resources in Interswitch, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Interswitch environment.
Why isw_reissue_card_pin is rated Medium
This tool modifies a cardholder's PIN, which is a security credential tied to financial access. While the action is technically reversible (a new PIN can be issued again), it represents a significant change to card security state and could lock out legitimate cardholders or enable fraud if misused by an AI agent. The requirement for 'confirm: true' indicates the developers recognize the sensitivity.
From the tool's definition Reissue a Card 360 card PIN - modifies card security credentials irreversibly. The tool changes authentication credentials for a payment card.
Attacks that exploit this kind of access
The rule that runs isw_reissue_card_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_reissue_card_pin, this is the rule to start with:
isw_reissue_card_pin stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Interswitch, apply this rule, and every isw_reissue_card_pin call is checked against it from then on.
Questions about isw_reissue_card_pin
Reissue a Card 360 card PIN. The plaintext pin is encrypted locally and never sent. Requires confirm: true. It is categorised as a Write tool in the Interswitch MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Interswitch MCP server in PolicyLayer and add a rule for isw_reissue_card_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.
isw_reissue_card_pin is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the isw_reissue_card_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.
Set action: deny in the PolicyLayer policy for isw_reissue_card_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.
isw_reissue_card_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.
More on Interswitch, and thousands of servers like it.
This server
Across the catalogue