get_nft_history

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What get_nft_history does on VaultPilot MCP

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

Parameter	Type	Required	Description
`limit`	integer	—	Max merged items to return (newest-first). Default 25, capped at 100 to keep the cross-chain merge bounded.
`chains`	array	—	Subset of supported EVM chains to scan. Omit for all five. Multi-chain results are merged + sorted desc by timestamp.
`wallet`	string	Yes

Parameters from the server's own tool schema.

RISK

Why get_nft_history is rated Low

This tool queries and returns NFT transaction history for a wallet without modifying state, executing code, or triggering external operations. The explicit 'Read-only' designation and data retrieval semantics confirm Read category. Severity is low because the blast radius of misuse is limited to information disclosure about a wallet's NFT activity, which is typically public blockchain data.

From the tool's definition "Recent NFT activity for a wallet" — retrieves historical data. "Read-only" explicitly stated. "mints, sales, transfers, listings (asks), bids, and cancels" — all query/retrieval operations with no 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 VaultPilot MCP, 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 VaultPilot MCP, 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? +

Recent NFT activity for a wallet across one or more supported EVM chains: mints, sales, transfers, listings (asks), bids, and cancels. Source: Reservoir's /users/{user}/activity/v6. Multi-chain results are merged + sorted by timestamp descending; capped at limit (default 25, max 100). Mirrors get_transaction_history's shape but limited to NFT-relevant events — same agent ergonomics, scoped to the NFT side of the wallet. EVM-only in v1; Solana deferred. Read-only. It is categorised as a Read tool in the VaultPilot MCP MCP Server, which means it retrieves data without modifying state.

What parameters does get_nft_history accept? +

get_nft_history accepts 3 parameters: limit, chains, wallet. Required: wallet. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_nft_history? +

Register the VaultPilot 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 VaultPilot MCP. 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 VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot 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 →