Low Risk

get_nft_history

Get the transfer history of NFTs in a collection.

Part of the Aibtc MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call get_nft_history to retrieve information from Aibtc without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though get_nft_history only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-aibtcdev-mcp-server.yaml
tools:
  get_nft_history:
    rules:
      - action: allow

See the full Aibtc policy for all 288 tools.

Tool Name get_nft_history
Category Read
MCP Server Aibtc MCP Server
Risk Level Low

View all 288 tools →

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? +

Add a rule in your Intercept YAML policy under the tools section for get_nft_history. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Aibtc MCP server.

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 Intercept 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 Intercept 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 (@aibtc/mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Aibtc

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.