Get list of FPX banks for online banking payments
AI agents call get_fpx_banks to retrieve information from Bayarcash MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static reference data (a list of FPX banks) for informational purposes. It has no side effects, does not modify any data, does not execute external operations with variable outcomes, and does not involve financial transactions. It is purely a data lookup to populate UI options or validate payment channels.
From the tool's definition Tool name 'get_fpx_banks' and description 'Get list of FPX banks for online banking payments' indicate a retrieval operation that queries available payment methods without modifying, deleting, or executing code.
Attacks that exploit this kind of access
Get list of FPX banks for online banking payments. It is categorised as a Read tool in the Bayarcash MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bayarcash MCP Server MCP server in PolicyLayer and add a rule for get_fpx_banks: 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 Bayarcash MCP Server. Nothing to install.
get_fpx_banks 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 get_fpx_banks 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 get_fpx_banks. 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.
get_fpx_banks is provided by the Bayarcash MCP Server MCP server (khairulimran-97/bayarcash-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →