Get information about an ERC721 NFT including metadata URI
AI agents call get_nft_info to retrieve information from EVM 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 NFT metadata and URI information from a blockchain, which is a non-destructive query operation. It has no side effects, does not transfer assets, execute code, or modify data. The blast radius of misuse is minimal—an agent could only access publicly available blockchain data. It aligns with the 'Read' category alongside sibling tools like 'get_balance', 'get_block', and 'get_contract_abi'.
From the tool's definition Tool name 'get_nft_info' and description 'Get information about an ERC721 NFT including metadata URI' indicate a read-only operation that retrieves and queries NFT data without modifying state or performing transactions.
Documented attack patterns abuse exactly the kind of access get_nft_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and EVM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_nft_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_nft_info": {}
}
} get_nft_info 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 information about an ERC721 NFT including metadata URI. It is categorised as a Read tool in the EVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EVM MCP Server MCP server in PolicyLayer and add a rule for get_nft_info: 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 EVM MCP Server. Nothing to install.
get_nft_info 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_info 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_info. 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_info is provided by the EVM MCP Server MCP server (mcpdotdirect/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from EVM MCP Server, 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.
25 EVM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.