Resolve an XLS-40 DID object for an XRPL account or did:xrpl identifier. Returns raw ledger data, UTF-8 decoded DID fields where valid, and fetched DID document content for ipfs:// or https:// URIs. Only text/JSON documents are inlined; binary content is reported as metadata (source, content type...
AI agents call did_resolve 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 only retrieves and resolves DID information from the XRPL ledger and external URIs (IPFS/HTTPS). It has no write or side-effect operations — it purely reads and returns data. The only mild concern is fetching external URIs, but the tool explicitly limits responses to metadata for binary content, keeping blast radius low.
From the tool's definition Resolve an XLS-40 DID object... Returns raw ledger data, UTF-8 decoded DID fields... fetched DID document content... Only text/JSON documents are inlined; binary content is reported as metadata
Attacks that exploit this kind of access
Resolve an XLS-40 DID object for an XRPL account or did:xrpl identifier. Returns raw ledger data, UTF-8 decoded DID fields where valid, and fetched DID document content for ipfs:// or https:// URIs. Only text/JSON documents are inlined; binary content is reported as metadata (source, content type, byte length) with the body omitted. 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 did_resolve: 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.
did_resolve 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 did_resolve 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 did_resolve. 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.
did_resolve 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.
did_resolve 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 →