Get the transaction history for an XRP Ledger account.
AI agents call get_account_transactions to retrieve information from XRPL 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 historical transaction data from the blockchain. It performs no modifications, deletions, or external operations—only data retrieval. The verb 'Get' and context of querying transaction history confirm this is a read-only operation. Severity is low because accessing public blockchain transaction history poses minimal risk; the data is already public on the ledger and no state changes occur.
From the tool's definition Tool name 'get_account_transactions' and description 'Get the transaction history for an XRP Ledger account' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_account_transactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and XRPL MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_account_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"get_account_transactions": {}
}
} get_account_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the transaction history for an XRP Ledger account. It is categorised as a Read tool in the XRPL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the XRPL MCP Server MCP server in PolicyLayer and add a rule for get_account_transactions: 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 Server. Nothing to install.
get_account_transactions 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_transactions 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_transactions. 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_transactions is provided by the XRPL MCP Server MCP server (lgcarrier/xrpl-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from XRPL MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 XRPL MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.