Get ETH, stETH, and wstETH balances for a given Ethereum address.
AI agents call lido_get_balances to retrieve information from Lido MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns balance information for blockchain tokens. It performs a read-only operation that retrieves existing data without creating, modifying, executing transactions, deleting data, or moving funds. The read-only nature and lack of state-changing operations clearly place it in the Read category with low severity.
From the tool's definition Tool name 'lido_get_balances' and description 'Get ETH, stETH, and wstETH balances for a given Ethereum address' indicate retrieval of balance data with no modification or side effects.
Attacks that exploit this kind of access
Get ETH, stETH, and wstETH balances for a given Ethereum address. It is categorised as a Read tool in the Lido MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Lido MCP Server MCP server in PolicyLayer and add a rule for lido_get_balances: 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 Lido MCP Server. Nothing to install.
lido_get_balances 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 lido_get_balances 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 lido_get_balances. 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.
lido_get_balances is provided by the Lido MCP Server MCP server (the-wunmi/lido-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 →