isw_deactivate_paycode

Deactivate an unused paycode. Requires confirm: true.

SERVERInterswitch SOURCEinterswitch-mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dairus01-interswitch-mcp-server/isw-deactivate-paycode.md

What isw_deactivate_paycode does on Interswitch

AI agents call isw_deactivate_paycode to permanently remove resources in Interswitch, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why isw_deactivate_paycode is rated Critical

Deactivating a paycode removes its ability to be used for payments, which is a destructive action in the financial domain. While it does not directly move money, it permanently disables a financial instrument. The mandatory confirmation flag further signals irreversibility. Classified as Destructive over Financial because no money is transferred — a payment instrument is disabled.

From the tool's definition 'Deactivate an unused paycode' — deactivation of a paycode is an irreversible or hard-to-reverse action that renders the paycode unusable; 'Requires confirm: true' implies a high-impact, non-trivial operation.

Questions about isw_deactivate_paycode

What does the isw_deactivate_paycode tool do? +

Deactivate an unused paycode. Requires confirm: true. It is categorised as a Destructive tool in the Interswitch MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on isw_deactivate_paycode? +

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

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

Can I rate-limit isw_deactivate_paycode? +

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

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Interswitch's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.