Revoke an identity by DID. Cascades JWT invalidation through the
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.
Revocation of a DID (Decentralized Identifier) and cascading JWT invalidation is an irreversible operation that destroys authentication credentials and identity state. Once revoked, the identity and all associated tokens cannot be recovered without re-issuance, making this a destructive action.
From the tool's definition 'Revoke an identity by DID. Cascades JWT invalidation through the' - the term 'revoke' indicates irreversible invalidation of identity credentials and authentication tokens.
Attacks that exploit this kind of access
Revoke an identity by DID. Cascades JWT invalidation through the. 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.
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.
revoke_did is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →