Monitor the NFT market: floor prices, 24h/7d volume, blue-chip collection sentiment, wash trade detection, and overall market health signal. Use this tool when: - A crypto agent wants to assess NFT market conditions as a risk-on/risk-off signal - You need floor prices for specific collections bef...
AI agents call get_nft_market to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries NFT market data with no side effects or ability to modify state. It is fundamentally a Read operation that gathers market intelligence. Severity is medium rather than low because an AI agent could use market data (floor prices, sentiment, wash trade signals) to inform financial decisions in a pay-per-call DeFi context, but the tool itself performs no writes, executions, or financial…
From the tool's definition Tool description states 'Monitor the NFT market: floor prices, 24h/7d volume, blue-chip collection sentiment, wash trade detection, and overall market health signal' and use cases specify 'assess NFT market conditions', 'floor prices for specific…
Attacks that exploit this kind of access
Monitor the NFT market: floor prices, 24h/7d volume, blue-chip collection sentiment, wash trade detection, and overall market health signal. Use this tool when: - A crypto agent wants to assess NFT market conditions as a risk-on/risk-off signal - You need floor prices for specific collections before making a purchase decision - An agent is detecting wash trading to identify manipulated volume - A DeFi agent wants to assess NFT-backed lending risks Returns per collection: name, floor_price_eth/usd, 24h_volume_eth, 7d_change_pct, unique_buyers_24h, wash_trade_pct, listing_ratio, market_signal (BULLISH/BEARISH/NEUTRAL). Example: getNftMarket({ collections:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_nft_market: 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 Omni Service Node. Nothing to install.
get_nft_market 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_market 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_market. 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_market is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). 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 →