This record as markdown: /tools/romthpt-mcp-xrpl/get-account-info.md
What get-account-info does on Xrpl mcp
AI agents call get-account-info 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 get-account-info is rated Low
This tool retrieves account data from a blockchain ledger without creating, modifying, deleting, or executing any operations. It is a pure query operation with no side effects. The blast radius of misuse is limited to information disclosure, which is low severity on a public ledger where account information may already be visible.
From the tool's definition Tool name is 'get-account-info' and description states 'Get account information from the XRP Ledger'. The verb 'Get' and lack of any modification language indicates a retrieval operation.
Attacks that exploit this kind of access
The rule that runs get-account-info 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 get-account-info, this is the rule to start with:
get-account-info 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 get-account-info call is checked against it from then on.
Questions about get-account-info
Get account information from the XRP Ledger. 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 get-account-info: 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.
get-account-info 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-account-info 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-account-info. 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-account-info 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