Critical Risk →

identity_unset_wallet

Remove the agent wallet association from an agent identity in the ERC-8004 identity registry. Requires an unlocked wallet.

Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@aibtc/mcp-server Destructive

AI agents may call identity_unset_wallet to permanently remove or destroy resources in Aibtc. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call identity_unset_wallet in a loop, permanently destroying resources in Aibtc. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-aibtcdev-mcp-server.yaml
tools:
  identity_unset_wallet:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Aibtc policy for all 308 tools.

Tool Name identity_unset_wallet
Category Destructive
MCP Server Aibtc MCP Server
Risk Level Critical

View all 308 tools →

Agents calling destructive-class tools like identity_unset_wallet have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

identity_unset_wallet is one of the critical-risk operations in Aibtc. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the identity_unset_wallet tool do? +

Remove the agent wallet association from an agent identity in the ERC-8004 identity registry. Requires an unlocked wallet.. 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.

How do I enforce a policy on identity_unset_wallet? +

Add a rule in your Intercept YAML policy under the tools section for identity_unset_wallet. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.

What risk level is identity_unset_wallet? +

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.

Can I rate-limit identity_unset_wallet? +

Yes. Add a rate_limit block to the identity_unset_wallet rule in your Intercept 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 identity_unset_wallet completely? +

Set action: deny in the Intercept 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.

What MCP server provides identity_unset_wallet? +

identity_unset_wallet is provided by the Aibtc MCP server (@aibtc/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.