Get transfer history for NFTs
AI agents call get_nft_transfers to retrieve information from Web3 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves transfer history for NFTs—purely a data query operation with no side effects. It does not create, modify, delete, execute code, or move assets. The blast radius of misuse is minimal, limited to potential information disclosure about NFT movement patterns.
From the tool's definition Tool name 'get_nft_transfers' and description 'Get transfer history for NFTs' indicate querying/retrieving historical data without modification or execution of operations. The verb 'Get' and context of 'history' confirm read-only retrieval.
Documented attack patterns abuse exactly the kind of access get_nft_transfers gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Web3, and nothing reaches the server without passing your rules. This is the rule we recommend for get_nft_transfers:
{
"version": "1",
"default": "deny",
"tools": {
"get_nft_transfers": {}
}
}get_nft_transfers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get transfer history for NFTs. It is categorised as a Read tool in the Web3 MCP Server, which means it retrieves data without modifying state.
Register the Web3 MCP server in PolicyLayer and add a rule for get_nft_transfers: 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 Web3. Nothing to install.
get_nft_transfers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_nft_transfers 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 get_nft_transfers. 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.
get_nft_transfers is provided by the Web3 MCP server (tumf/web3-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Web3, 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.
17 Web3 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.