isw_agency_requery_xml
Submit raw Agency Banking requery XML.
This record as markdown: /tools/io-github-dairus01-interswitch-mcp-server/isw-agency-requery-xml.md
What isw_agency_requery_xml does on Interswitch
AI agents invoke isw_agency_requery_xml to trigger actions in Interswitch. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why isw_agency_requery_xml is rated High
This tool submits raw XML to the Agency Banking system to requery transactions. Executing raw XML payloads against a financial banking API is an Execute-level action — it triggers external operations whose effects depend on the submitted XML content. While a 'requery' is typically a status check (Read), submitting raw XML introduces execution risk as the payload content determines the actual operation.
From the tool's definition Submit raw Agency Banking requery XML
Attacks that exploit this kind of access
The rule that runs isw_agency_requery_xml 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_agency_requery_xml, this is the rule to start with:
isw_agency_requery_xml stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_agency_requery_xml call is checked against it from then on.
Questions about isw_agency_requery_xml
Submit raw Agency Banking requery XML. 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.
Register the Interswitch MCP server in PolicyLayer and add a rule for isw_agency_requery_xml: 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_agency_requery_xml is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the isw_agency_requery_xml 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_agency_requery_xml. 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_agency_requery_xml 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.
Across the catalogue