deactivate-did

THE RISK

Critical Risk

Why deactivate-did needs a policy

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

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

POLICY

How to control deactivate-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 deactivate-did:

policy.json

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

deactivate-did disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

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.

RESTRICT 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 →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Xrpl mcp → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

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.

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 →