Transfer an NFT from the connected wallet to another address
AI agents use transferERC721 to commit financial operations through MCP Ethers Wallet — usually the final step of a payment, billing, or trading workflow. A call moves real money.
While the tool could be categorized as 'Write' or 'Execute' due to its blockchain state-modification nature, it is most accurately classified as 'Financial' because it transfers ownership of non-fungible tokens (NFTs) between addresses. NFTs frequently represent valuable digital assets, collectibles, or rights.
From the tool's definition The tool performs 'Transfer an NFT from the connected wallet to another address,' which moves digital assets (ERC721 tokens) from one wallet to another. NFTs represent ownership of unique assets with real-world and financial value.
Documented attack patterns abuse exactly the kind of access transferERC721 gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Ethers Wallet, and nothing reaches the server without passing your rules. This is the rule we recommend for transferERC721:
{
"version": "1",
"default": "deny",
"tools": {
"transferERC721": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to transferERC721 is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer an NFT from the connected wallet to another address. It is categorised as a Financial tool in the MCP Ethers Wallet MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the MCP Ethers Wallet MCP server in PolicyLayer and add a rule for transferERC721: 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 MCP Ethers Wallet. Nothing to install.
transferERC721 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 transferERC721 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 transferERC721. 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.
transferERC721 is provided by the MCP Ethers Wallet MCP server (crazyrabbitltc/mcp-ethers-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Ethers Wallet, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
69 MCP Ethers Wallet tools catalogued and risk-classified — across an index of 43,000+ MCP servers.