Get user token balance on a specific chain
AI agents call get_user_balance to retrieve information from ValueRouter MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely queries and returns balance information. It does not create, modify, delete, execute code, or commit financial transactions. While the server context involves bridging USDC (a financial asset), this specific tool is a non-destructive data retrieval operation.
From the tool's definition Tool name 'get_user_balance' and description 'Get user token balance on a specific chain' indicate a read-only query operation that retrieves data without modification, side effects, or external state changes.
Attacks that exploit this kind of access
Get user token balance on a specific chain. It is categorised as a Read tool in the ValueRouter MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ValueRouter MCP Server MCP server in PolicyLayer and add a rule for get_user_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 ValueRouter MCP Server. Nothing to install.
get_user_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_user_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_user_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_user_balance is provided by the ValueRouter MCP Server MCP server (rwavaluerouter/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 →