Get live data on AI agents from the Virtuals Protocol ecosystem: token prices, market cap, 24h volume, trading activity, and rankings by agent activity score. Use this tool when: - An agent is investing in or monitoring AI agent tokens in the Virtuals ecosystem - You need to track the performance...
AI agents call get_virtuals_protocol 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 is a Read tool—it queries and retrieves market data about cryptocurrency tokens without side effects. However, severity is elevated to 'medium' because: (1) the server operates on 'USDC on Base Mainnet via x402' indicating financial infrastructure; (2) an AI agent could use this data to make or influence high-value trading decisions; (3) the tool provides real-time market signals that could be misused to…
From the tool's definition Tool retrieves 'live data on AI agents from the Virtuals Protocol ecosystem: token prices, market cap, 24h volume, trading activity, and rankings'.
Attacks that exploit this kind of access
Get live data on AI agents from the Virtuals Protocol ecosystem: token prices, market cap, 24h volume, trading activity, and rankings by agent activity score. Use this tool when: - An agent is investing in or monitoring AI agent tokens in the Virtuals ecosystem - You need to track the performance of specific Virtuals agents (LUNA, AIXBT, etc.) - A research agent is analysing the on-chain AI agent economy - You want to identify the most active and valuable AI agents by market metrics Returns per agent: agent_name, token_ticker, price_usd, market_cap, 24h_volume, 24h_change_pct, activity_score, holder_count, chain. Example: getVirtualsProtocol({ limit: 10 }) → LUNA $0.84 (+12%), AIXBT $0.23 (-3%), top 10 by market cap. Cost: $0.005 USDC per call. 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_virtuals_protocol: 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_virtuals_protocol 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_virtuals_protocol 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_virtuals_protocol. 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_virtuals_protocol 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 →