Decode a signed XRPL transaction blob, compute its hash, and optionally compare it against an expected partial intent before submission. This is the WYSIWYS safety gate.
AI agents call tx_decode_verify to retrieve information from Xrpl Identity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs cryptographic and structural inspection of pre-signed transaction data without executing, modifying, or deleting anything. It is explicitly a safety verification step prior to submission, making it purely a Read operation with minimal risk — appropriate for AI agents to use for transaction validation before committing to execution.
From the tool's definition Tool description explicitly states 'Decode a signed XRPL transaction blob, compute its hash, and optionally compare it against an expected partial intent before submission.' The verbs are 'decode', 'compute', and 'compare' — all read-only inspection…
Attacks that exploit this kind of access
Decode a signed XRPL transaction blob, compute its hash, and optionally compare it against an expected partial intent before submission. This is the WYSIWYS safety gate. It is categorised as a Read tool in the Xrpl Identity MCP Server, which means it retrieves data without modifying state.
Register the Xrpl Identity MCP server in PolicyLayer and add a rule for tx_decode_verify: 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 Identity. Nothing to install.
tx_decode_verify 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 tx_decode_verify 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 tx_decode_verify. 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.
tx_decode_verify is provided by the Xrpl Identity MCP server (jarod-vyent/xrpl-identity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
tx_decode_verify is one line of Xrpl Identity's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →