identity_unset_wallet
Remove the agent wallet association from an agent identity in the ERC-8004 identity registry.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/identity-unset-wallet.md
What identity_unset_wallet does on Aibtc
AI agents call identity_unset_wallet to permanently remove resources in Aibtc, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why identity_unset_wallet is rated Critical
The tool irreversibly removes/disassociates a wallet from an agent identity in a registry. This is a destructive operation that unlinks critical identity-to-wallet bindings, which could have severe consequences if misused by an AI agent (e.g., locking out access to funds or identity). 'Remove' implies an unrecoverable or difficult-to-reverse action on a blockchain/registry context.
From the tool's definition Remove the agent wallet association from an agent identity in the ERC-8004 identity registry
Attacks that exploit this kind of access
The rule that runs identity_unset_wallet safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For identity_unset_wallet, this is the rule to start with:
identity_unset_wallet is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every identity_unset_wallet call is checked against it from then on.
Questions about identity_unset_wallet
Remove the agent wallet association from an agent identity in the ERC-8004 identity registry. It is categorised as a Destructive tool in the Aibtc MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for identity_unset_wallet: 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 Aibtc. Nothing to install.
identity_unset_wallet 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 identity_unset_wallet 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 identity_unset_wallet. 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.
identity_unset_wallet is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aibtc, and thousands of servers like it.
Across the catalogue