isw_get_paycode_status
Get status of a generated paycode.
This record as markdown: /tools/io-github-dairus01-interswitch-mcp-server/isw-get-paycode-status.md
What isw_get_paycode_status does on Interswitch
AI agents call isw_get_paycode_status 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.
Why isw_get_paycode_status is rated Low
This tool queries the status of an existing paycode. It performs read-only retrieval of information with no capability to create, modify, delete, or trigger financial transactions. The 'get' verb and 'status' query nature confirm it is a Read category tool. Severity is low because status checks have minimal blast radius even if misused by an agent.
From the tool's definition Tool name includes 'get' and description states 'Get status of a generated paycode' — a pure query operation that retrieves existing data without modification or side effects.
Attacks that exploit this kind of access
The rule that runs isw_get_paycode_status 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_paycode_status, this is the rule to start with:
isw_get_paycode_status is read-only, so it stays allowed. 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_get_paycode_status call is checked against it from then on.
Questions about isw_get_paycode_status
Get status of a generated paycode. It is categorised as a Read tool in the Interswitch MCP Server, which means it retrieves data without modifying state.
Register the Interswitch MCP server in PolicyLayer and add a rule for isw_get_paycode_status: 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_get_paycode_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the isw_get_paycode_status 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_get_paycode_status. 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_get_paycode_status 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