transfer_nft
Transfer an NFT (ERC721 token) from one address to another. Requires the private key of the current owner for signing the transaction.
This record as markdown: /tools/chulanpro5-evm-mcp-server/transfer-nft.md
What transfer_nft does on EVM MCP Server
AI agents use transfer_nft to commit financial operations through EVM MCP Server, usually the final step of a payment, billing, or trading workflow. A call moves real money.
Why transfer_nft is rated Critical
Transferring an NFT is a financial operation as it moves a potentially valuable digital asset (NFT) between addresses on the blockchain. This is irreversible once confirmed on-chain, and misuse could result in permanent loss of valuable assets. The requirement for a private key signing makes this a real, committed blockchain transaction with financial consequences.
From the tool's definition Transfer an NFT (ERC721 token) from one address to another. Requires the private key of the current owner for signing the transaction.
Attacks that exploit this kind of access
The rule that runs transfer_nft safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EVM MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For transfer_nft, this is the rule to start with:
Any call to transfer_nft is blocked until a human approves it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EVM MCP Server, apply this rule, and every transfer_nft call is checked against it from then on.
Questions about transfer_nft
Transfer an NFT (ERC721 token) from one address to another. Requires the private key of the current owner for signing the transaction. It is categorised as a Financial tool in the EVM MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the EVM MCP Server MCP server in PolicyLayer and add a rule for transfer_nft: 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 EVM MCP Server. Nothing to install.
transfer_nft 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 transfer_nft 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 transfer_nft. 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.
transfer_nft is provided by the EVM MCP Server MCP server (chulanpro5/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EVM MCP Server, and thousands of servers like it.
Across the catalogue