Get wallet balance
AI agents call get-balance to retrieve information from Cryptocurrency Daemon MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves wallet balance information without side effects. While it accesses sensitive financial data, reading balance information is a non-destructive query operation. It does not move funds, execute transactions, or modify state. The presence of sibling tools like 'send-coins' and 'zsend-coins' confirms those are the financial/destructive operations, whereas get-balance is purely informational.
From the tool's definition Tool name and description indicate data retrieval only: 'Get wallet balance'. No modifications, deletions, or financial transactions are performed.
Attacks that exploit this kind of access
Get wallet balance. It is categorised as a Read tool in the Cryptocurrency Daemon MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Cryptocurrency Daemon MCP 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 Cryptocurrency Daemon MCP 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 Cryptocurrency Daemon MCP Server MCP server (raw391/coin_daemon_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 →