This record as markdown: /tools/nirholas-agenti/get-balance.md
What get_balance does on Agenti
AI agents call get_balance to retrieve information from Agenti without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_balance is rated Low
This tool queries financial account data but does not move, spend, or commit funds. It is a pure read operation that retrieves current balance information. While the server context involves cryptocurrency operations, this specific tool only retrieves data without enabling any financial transactions or state changes. Confidence is high because the description is explicit and unambiguous about its read-only function.
From the tool's definition Tool description states 'Get USDC (Base) and SOL balances for a wallet' — a retrieval operation with no side effects. The verb 'Get' and the read-only nature of querying account balances are definitive.
Attacks that exploit this kind of access
The rule that runs get_balance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agenti, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_balance, this is the rule to start with:
get_balance is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agenti, apply this rule, and every get_balance call is checked against it from then on.
Questions about get_balance
Get USDC (Base) and SOL balances for a wallet. It is categorised as a Read tool in the Agenti MCP Server, which means it retrieves data without modifying state.
Register the Agenti 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 Agenti. 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 Agenti MCP server (nirholas/agenti). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agenti, and thousands of servers like it.
This server
Across the catalogue