create-did

Create a decentralized identifier (DID) for an XRPL account

SERVERXrpl mcp SOURCEromthpt/mcp-xrpl

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/romthpt-mcp-xrpl/create-did.md

WHAT IT DOES

What create-did does on Xrpl mcp

AI agents use create-did to create or update resources in Xrpl mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xrpl mcp environment.

RISK

Why create-did is rated Medium

This tool creates a new DID associated with an XRPL account, which is a reversible write operation (DIDs can typically be deleted or modified). It does not execute arbitrary code, delete data, move funds, or query existing data; it explicitly creates a new ledger object.

From the tool's definition Tool description states 'Create a decentralized identifier (DID) for an XRPL account' — the verb 'create' indicates the tool creates and stores new data on the ledger that persists.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create-did safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Xrpl mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create-did, this is the rule to start with:

create-did Rate-limited

create-did stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create-did": {
      "limits": [
        {
          "counter": "create-did_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Xrpl mcp, apply this rule, and every create-did call is checked against it from then on.

FAQ

Questions about create-did

What does the create-did tool do? +

Create a decentralized identifier (DID) for an XRPL account. It is categorised as a Write tool in the Xrpl mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

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

Register the Xrpl MCP server in PolicyLayer and add a rule for create-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 create-did? +

create-did is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create-did? +

Yes. Add a rate_limit block to the create-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 create-did completely? +

Set action: deny in the PolicyLayer policy for create-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 create-did? +

create-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.

KEEP EXPLORING

More on Xrpl, and thousands of servers like it.

This server

All 71 Xrpl tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →