get_nft_history

Get the transfer history of NFTs in a collection.

SERVERAibtc SOURCEaibtcdev/aibtc-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/io-github-aibtcdev-mcp-server/get-nft-history.md

WHAT IT DOES

What get_nft_history does on Aibtc

AI agents call get_nft_history to retrieve information from Aibtc without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_nft_history is rated Low

The tool queries historical data about NFT transfers. It performs a read-only operation that retrieves information without creating, modifying, deleting, or executing any actions. The most severe risk is accidental information exposure, which is minimal for historical public blockchain data.

From the tool's definition Tool description states 'Get the transfer history of NFTs in a collection.' This is a retrieval operation with no indication of modification, deletion, or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_nft_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Aibtc, 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 Allowed

get_nft_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_nft_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aibtc, apply this rule, and every get_nft_history call is checked against it from then on.

FAQ

Questions about get_nft_history

What does the get_nft_history tool do? +

Get the transfer history of NFTs in a collection. It is categorised as a Read tool in the Aibtc MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_nft_history? +

Register the Aibtc 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 Aibtc. Nothing to install.

What risk level is get_nft_history? +

get_nft_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_nft_history? +

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.

How do I block get_nft_history completely? +

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.

What MCP server provides get_nft_history? +

get_nft_history is provided by the Aibtc MCP server (aibtcdev/aibtc-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Aibtc, and thousands of servers like it.

This server

All 358 Aibtc tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →