Retrieve the audit log of all signing and transaction operations, optionally filtered by wallet, tool, or network.
AI agents call get-audit-log to retrieve information from Xrpl mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries audit log data for signing and transaction operations. It performs no modifications, deletions, or external operations—only retrieval of existing records. The sibling tools on this server include destructive operations (amm-delete, amm-clawback) and financial operations (batch-payment, approve-token-spending), making the read-only nature of get-audit-log clear.
From the tool's definition Tool name contains 'get-' and description states 'Retrieve the audit log' with optional filtering parameters. This is a pure read operation that queries historical data without modification.
Documented attack patterns abuse exactly the kind of access get-audit-log gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xrpl mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for get-audit-log:
{
"version": "1",
"default": "deny",
"tools": {
"get-audit-log": {}
}
}get-audit-log 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.
Retrieve the audit log of all signing and transaction operations, optionally filtered by wallet, tool, or network. 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-audit-log: 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-audit-log 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-audit-log 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-audit-log. 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-audit-log 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.
Start from Xrpl mcp, 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.
71 Xrpl mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.