get_bnb_balance
AI agents call get_bnb_balance to retrieve information from FourTrader 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 data (BNB balance) without modifying state, executing code, or committing financial transactions. It is a passive query operation with no side effects. The empty description lowers confidence slightly, but the tool name and pattern of sibling tools strongly indicate a read-only balance lookup function.
From the tool's definition Tool name 'get_bnb_balance' indicates a query operation that retrieves wallet balance information. The naming convention aligns with other read-only tools on the server (get_bonding_curve_progress, get_latest_trades, get_token_balance, get_token_info,…
Attacks that exploit this kind of access
get_bnb_balance. It is categorised as a Read tool in the FourTrader MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FourTrader MCP Server MCP server in PolicyLayer and add a rule for get_bnb_balance: 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 FourTrader MCP Server. Nothing to install.
get_bnb_balance 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_bnb_balance 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_bnb_balance. 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_bnb_balance is provided by the FourTrader MCP Server MCP server (sunneeee/fourtrader-mcp). 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 →