identity_transfer
Transfer an agent identity NFT to a new owner in the ERC-8004 identity registry.
This record as markdown: /tools/io-github-aibtcdev-mcp-server/identity-transfer.md
What identity_transfer does on Aibtc
AI agents use identity_transfer to commit financial operations through Aibtc, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why identity_transfer is rated Critical
The tool transfers ownership of an NFT (non-fungible token), which represents real digital or financial value. This is a direct financial operation that moves an asset from one party to another and cannot be easily reversed. Although it could be classified as Destructive (irreversible), Financial is the most appropriate category because the primary intent and effect is the transfer of economic value/ownership rights.
From the tool's definition Tool description states it 'Transfer[s] an agent identity NFT to a new owner' — this is an ownership transfer of an NFT asset, which constitutes a financial commitment and irreversible movement of value.
Attacks that exploit this kind of access
The rule that runs identity_transfer 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_transfer, this is the rule to start with:
Any call to identity_transfer is blocked until a human approves 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_transfer call is checked against it from then on.
Questions about identity_transfer
Transfer an agent identity NFT to a new owner in the ERC-8004 identity registry. It is categorised as a Financial tool in the Aibtc MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Aibtc MCP server in PolicyLayer and add a rule for identity_transfer: 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_transfer is a Financial 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_transfer 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_transfer. 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_transfer 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