revoke_did

A destructive tool on the Tenzro Ledger MCP server.

SERVERTenzro Ledger MCP SOURCEhttps://canton-mcp.tenzro.network/mcp

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/network-tenzro-tenzro/revoke-did.md

WHAT IT DOES

What revoke_did does on Tenzro Ledger MCP

AI agents call revoke_did to permanently remove resources in Tenzro Ledger MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why revoke_did is rated Critical

Revoking a DID is typically an irreversible action that permanently invalidates an identity credential and all associated access rights, trust relationships, and mandates. Given the server context (identity, payments, agents, verification), a revoked DID could have broad downstream consequences.

From the tool's definition Tool name 'revoke_did' implies revocation of a Decentralized Identifier (DID); the description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs revoke_did safely

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

revoke_did Hidden

revoke_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": [
    "revoke_did"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tenzro Ledger MCP, apply this rule, and every revoke_did call is checked against it from then on.

FAQ

Questions about revoke_did

What does the revoke_did tool do? +

revoke_did is a destructive tool on the Tenzro Ledger MCP server. It is categorised as a Destructive tool in the Tenzro Ledger 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 revoke_did? +

Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for revoke_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 Tenzro Ledger MCP. Nothing to install.

What risk level is revoke_did? +

revoke_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 revoke_did? +

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

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

revoke_did is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tenzro Ledger, and thousands of servers like it.

This server

All 360 Tenzro Ledger tools → Critical-risk tools on this server →

Across the catalogue

web3_revoke_key on 0xarchive →revoke_api_token on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →