TDIP/GDPR Article 17 right-to-erasure. Hard-deletes a previously
AI agents call forget_identity 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.
The tool explicitly performs a 'hard-delete' of an identity record, invoking GDPR's right-to-erasure (Article 17). This is an irreversible destruction of identity data. Given the context of a wallet/identity/payments platform, erasing an identity could have cascading effects on associated wallets, payment credentials, agents, and staking positions — making this critical severity.
From the tool's definition TDIP/GDPR Article 17 right-to-erasure. Hard-deletes a previously
Attacks that exploit this kind of access
TDIP/GDPR Article 17 right-to-erasure. Hard-deletes a previously. 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 forget_identity: 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.
forget_identity 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 forget_identity 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 forget_identity. 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.
forget_identity 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 →