Get the token URI/metadata for a specific NFT
AI agents call get_nft_token_uri to retrieve information from Stacks AI 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 metadata for an NFT (a token URI) without modifying, deleting, or executing any operations. It is a simple read-only query operation typical of blockchain data retrieval. Even in the context of a DeFi server with financial tools, this specific tool performs only data retrieval with no financial, destructive, or execution-related risks.
From the tool's definition Tool name 'get_nft_token_uri' and description 'Get the token URI/metadata for a specific NFT' both indicate a retrieval operation. The verb 'Get' explicitly denotes querying/fetching data with no side effects.
Attacks that exploit this kind of access
Get the token URI/metadata for a specific NFT. It is categorised as a Read tool in the Stacks AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stacks AI MCP Server MCP server in PolicyLayer and add a rule for get_nft_token_uri: 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 Stacks AI MCP Server. Nothing to install.
get_nft_token_uri 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_token_uri 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_token_uri. 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_token_uri is provided by the Stacks AI MCP Server MCP server (stack-ai-mcp/stacks-mcp-server). 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 →