This record as markdown: /tools/romthpt-mcp-xrpl/check-token-balance.md
What check-token-balance does on Xrpl mcp
AI agents call check-token-balance to retrieve information from Xrpl mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check-token-balance is rated Low
This tool queries account token balances on the XRP Ledger. It performs a read-only operation that retrieves data with no side effects. No data is created, modified, deleted, or financial transactions are executed. This is a simple informational lookup, making it a low-severity Read operation.
From the tool's definition Tool name 'check-token-balance' and description 'Check token balance for an address' indicate a query operation that retrieves balance information without modifying state.
Attacks that exploit this kind of access
The rule that runs check-token-balance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Xrpl mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check-token-balance, this is the rule to start with:
check-token-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 Xrpl mcp, apply this rule, and every check-token-balance call is checked against it from then on.
Questions about check-token-balance
Check token balance for an address. It is categorised as a Read tool in the Xrpl mcp MCP Server, which means it retrieves data without modifying state.
Register the Xrpl MCP server in PolicyLayer and add a rule for check-token-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 Xrpl mcp. Nothing to install.
check-token-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 check-token-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 check-token-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.
check-token-balance is provided by the Xrpl MCP server (romthpt/mcp-xrpl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Xrpl, and thousands of servers like it.
This server
Across the catalogue