Check the current SOL balance in your wallet
AI agents call get-balance to retrieve information from AI42-MCP X402 Payment Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves balance information; it has no capability to move funds, execute transactions, or modify any state. While it accesses financial data (SOL wallet balance), the action itself is purely informational. The severity is low because misuse by an AI agent would only expose account balance visibility, not enable actual financial harm.
From the tool's definition Tool performs 'Check the current SOL balance in your wallet' — a read-only query that retrieves financial account data without modifying it or executing transactions.
Attacks that exploit this kind of access
Check the current SOL balance in your wallet. It is categorised as a Read tool in the AI42-MCP X402 Payment Server MCP Server, which means it retrieves data without modifying state.
Register the AI42-MCP X402 Payment Server MCP server in PolicyLayer and add a rule for get-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 AI42-MCP X402 Payment Server. Nothing to install.
get-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-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-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-balance is provided by the AI42-MCP X402 Payment Server MCP server (kishore-mk/ai42-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 →