Get ERC721 transfers for a specific wallet address
AI agents call getERC721Transfers to retrieve information from Somnia MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical blockchain data about NFT (ERC721 token) transfers associated with a wallet. It queries existing data without side effects, creating no new transactions, modifying no balances, and executing no code. The blast radius of misuse is minimal—an attacker could enumerate transfer history but cannot manipulate assets or perform unauthorized actions.
From the tool's definition Tool name 'getERC721Transfers' and description 'Get ERC721 transfers for a specific wallet address' indicate data retrieval without modification.
Attacks that exploit this kind of access
Get ERC721 transfers for a specific wallet address. It is categorised as a Read tool in the Somnia MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Somnia MCP Server MCP server in PolicyLayer and add a rule for getERC721Transfers: 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 Somnia MCP Server. Nothing to install.
getERC721Transfers 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 getERC721Transfers 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 getERC721Transfers. 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.
getERC721Transfers is provided by the Somnia MCP Server MCP server (vastavikadi/somnia-mcp). 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 →