get_nft_history
Get NFT transaction history for an address
This record as markdown: /tools/stack-ai-mcp-stacks-mcp-server/get-nft-history.md
What get_nft_history does on Stacks AI MCP Server
AI agents call get_nft_history to retrieve information from Stacks AI MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_nft_history is rated Low
This tool retrieves and displays past transaction records for NFTs associated with a blockchain address. It performs a read-only query with no side effects, no code execution, no data modification, and no financial transactions. The blast radius of misuse is minimal—an agent could retrieve historical data it shouldn't see, but cannot cause irreversible damage or financial loss.
From the tool's definition Tool name 'get_nft_history' and description 'Get NFT transaction history for an address' indicate a retrieval operation that queries historical data without modifying or executing state-changing operations.
Attacks that exploit this kind of access
The rule that runs get_nft_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stacks AI MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_nft_history, this is the rule to start with:
get_nft_history 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 Stacks AI MCP Server, apply this rule, and every get_nft_history call is checked against it from then on.
Questions about get_nft_history
Get NFT transaction history for an address. 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_history: 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_history 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_history 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_history. 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_history 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.
More on Stacks AI MCP Server, and thousands of servers like it.
This server
Across the catalogue