resolve-did

THE RISK

Low Risk

Why resolve-did needs a policy

This tool reads/fetches a DID (Decentralized Identifier) document from the XRP Ledger. It only retrieves data with no side effects, making it a Read operation with low severity.

From the tool's definition Resolve a DID to retrieve its DID document

Documented attack patterns abuse exactly the kind of access resolve-did gives an agent:

POLICY

How to control resolve-did

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 resolve-did:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resolve-did": {}
  }
}

resolve-did is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Xrpl mcp — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Xrpl mcp tools

Financial amm-deposit Deposit assets into an existing Automated Market Maker (AMM) on the XRP Ledger Financial transfer-token Transfer tokens between addresses Financial transfer-xrp Transfer XRP between accounts using the connected wallet or a named wallet Financial check-cash Cash a Check to receive funds from it Financial amm-bid Place a bid on an Automated Market Maker Financial amm-clawback Clawback assets from an Automated Market Maker (AMM) Financial amm-create Create a new Automated Market Maker (AMM) on the XRP Ledger Financial approve-transaction Approve a pending transaction, signing and submitting it to the XRP Ledger. This is a dest

All 71 Xrpl mcp tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about resolve-did

What does the resolve-did tool do? +

Resolve a DID to retrieve its DID document. It is categorised as a Read tool in the Xrpl mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on resolve-did? +

Register the Xrpl MCP server in PolicyLayer and add a rule for resolve-did: 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.

What risk level is resolve-did? +

resolve-did is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit resolve-did? +

Yes. Add a rate_limit block to the resolve-did 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.

How do I block resolve-did completely? +

Set action: deny in the PolicyLayer policy for resolve-did. 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.

What MCP server provides resolve-did? +

resolve-did 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.

Enforce policy on every Xrpl mcp tool call.

Start from Xrpl mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →