transfer_nft

Transfer an NFT (ERC721 token) from one address to another.

SERVERSEI MCP Server V2 SOURCEtestinguser1111111/sei-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/testinguser1111111-sei-mcp-server/transfer-nft.md

WHAT IT DOES

What transfer_nft does on SEI MCP Server V2

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.

RISK

Why transfer_nft is rated Medium

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

RECOMMENDED RULE

The rule that runs transfer_nft safely

PolicyLayer is an MCP gateway: it sits between your AI agents and SEI MCP Server V2, 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:

transfer_nft Rate-limited

transfer_nft stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "transfer_nft": {
      "limits": [
        {
          "counter": "transfer_nft_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SEI MCP Server V2, apply this rule, and every transfer_nft call is checked against it from then on.

FAQ

Questions about transfer_nft

What does the transfer_nft tool do? +

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.

How do I enforce a policy on transfer_nft? +

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.

What risk level is transfer_nft? +

transfer_nft is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit transfer_nft? +

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.

How do I block transfer_nft completely? +

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.

What MCP server provides transfer_nft? +

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.

KEEP EXPLORING

More on SEI MCP Server V2, and thousands of servers like it.

This server

All 187 SEI MCP Server V2 tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →