getNFTMetadata
Gets metadata for an NFT token by contract address and token ID
This record as markdown: /tools/nanidao-agentek/getnftmetadata.md
What getNFTMetadata does on Agentek Eth
AI agents call getNFTMetadata to retrieve information from Agentek Eth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why getNFTMetadata is rated Low
This tool queries and retrieves NFT metadata without modifying, executing operations, deleting data, or moving funds. It is a read-only operation that fetches information from the blockchain. The severity is low as misuse would only expose or return publicly available metadata without causing harm.
From the tool's definition Tool description states 'Gets metadata for an NFT token by contract address and token ID' - a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs getNFTMetadata safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agentek Eth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getNFTMetadata, this is the rule to start with:
getNFTMetadata is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Agentek Eth, apply this rule, and every getNFTMetadata call is checked against it from then on.
Questions about getNFTMetadata
Gets metadata for an NFT token by contract address and token ID. It is categorised as a Read tool in the Agentek Eth MCP Server, which means it retrieves data without modifying state.
Register the Agentek Eth MCP server in PolicyLayer and add a rule for getNFTMetadata: 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 Agentek Eth. Nothing to install.
getNFTMetadata 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 getNFTMetadata 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 getNFTMetadata. 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.
getNFTMetadata is provided by the Agentek Eth MCP server (nanidao/agentek). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agentek Eth, and thousands of servers like it.
This server
Across the catalogue