update-did

Update a DID document with new properties

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/update-did.md

WHAT IT DOES

What update-did does on Xrpl mcp

AI agents use update-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 update-did is rated Medium

This tool creates or modifies data reversibly by updating DID (Decentralized Identifier) documents with new properties. The operation is Write-category because it changes ledger state but does not irreversibly destroy data (Destructive), execute arbitrary code (Execute), or move funds (Financial).

From the tool's definition Tool name 'update-did' and description 'Update a DID document with new properties' indicate modification of existing data (DID documents) on the XRP Ledger.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update-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 update-did, this is the rule to start with:

update-did Rate-limited

update-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": {
    "update-did": {
      "limits": [
        {
          "counter": "update-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 update-did call is checked against it from then on.

FAQ

Questions about update-did

What does the update-did tool do? +

Update a DID document with new properties. 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 update-did? +

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

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

Can I rate-limit update-did? +

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

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

update-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

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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