AI agents call wallet_balance to retrieve information from CorteX402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
wallet_balance retrieves financial information about a blockchain wallet without modifying state, transferring funds, or executing arbitrary code. It is a read operation with no side effects. While it concerns financial data, the tool itself does not move money or commit financial obligations—it only queries balance state.
From the tool's definition Tool name 'wallet_balance' indicates a balance query operation. The server description confirms this is a data product on Base mainnet that retrieves wallet balance information; no description provided for the tool itself.
Attacks that exploit this kind of access
wallet_balance. It is categorised as a Read tool in the CorteX402 MCP Server, which means it retrieves data without modifying state.
Register the CorteX402 MCP server in PolicyLayer and add a rule for wallet_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 CorteX402. Nothing to install.
wallet_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 wallet_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 wallet_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.
wallet_balance is provided by the CorteX402 MCP server (ooak21/cortex402-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 →