deactivate-did

Deactivate a DID by marking it as revoked

SERVERXrpl mcp SOURCEromthpt/mcp-xrpl

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What deactivate-did does on Xrpl mcp

AI agents call deactivate-did to permanently remove resources in Xrpl mcp, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why deactivate-did is rated Critical

Revoking/deactivating a Decentralized Identifier (DID) is an irreversible or at minimum highly consequential action that permanently marks the identity as revoked on the XRP Ledger blockchain. Blockchain-based revocation cannot be undone, making this Destructive. The blast radius is high since deactivating a DID can invalidate all credentials and authentication tied to that identity.

From the tool's definition Deactivate a DID by marking it as revoked

Attacks that exploit this kind of access

RECOMMENDED RULE

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

deactivate-did Hidden

deactivate-did is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "deactivate-did"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about deactivate-did

What does the deactivate-did tool do? +

Deactivate a DID by marking it as revoked. It is categorised as a Destructive tool in the Xrpl mcp MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

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

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

deactivate-did is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deactivate-did? +

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

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

deactivate-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 → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →