Transfer an NFT (ERC721 token) from one address to another.
AI agents use transfer_nft to create or update resources in SEI MCP Server V2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SEI MCP Server V2 environment.
This tool moves an NFT between addresses, which is a write operation that modifies on-chain ownership state. While it is reversible in theory (the recipient could transfer it back), unauthorized transfers could result in permanent loss of a valuable digital asset if the recipient is malicious or incorrect. The high severity reflects the potential for significant financial/asset loss if misused by an AI agent.
From the tool's definition Transfer an NFT (ERC721 token) from one address to another
Attacks that exploit this kind of access
Transfer an NFT (ERC721 token) from one address to another. It is categorised as a Write tool in the SEI MCP Server V2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SEI MCP Server V2 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 SEI MCP Server V2. Nothing to install.
transfer_nft is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). 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 →