Get cryptocurrency data. No arguments returns market overview; pass a symbol for detailed token data. WHEN TO USE: For crypto market cap overview or individual token data (price, supply, ATH). Use veroq_crypto_chart for price history. RETURNS: Overview: total market cap, BTC dominance, 24h volume...
AI agents call veroq_crypto to retrieve information from Veroq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval tool that queries and displays cryptocurrency market statistics. It performs no mutations, executes no code, triggers no trades, and commits no financial obligations. The 'Financial' category does not apply because the tool merely reports market data rather than executing trades, transfers, or financial commitments. Classification as Read is appropriate.
From the tool's definition Tool retrieves cryptocurrency market data and token information (price, supply, ATH, market cap, volume). Description explicitly states 'Get cryptocurrency data' with returns limited to informational metrics.
Attacks that exploit this kind of access
Get cryptocurrency data. No arguments returns market overview; pass a symbol for detailed token data. WHEN TO USE: For crypto market cap overview or individual token data (price, supply, ATH). Use veroq_crypto_chart for price history. RETURNS: Overview: total market cap, BTC dominance, 24h volume. Token: price, 24h/7d change, market cap, supply, ATH. COST: 2 credits. EXAMPLE: {. It is categorised as a Read tool in the Veroq MCP Server, which means it retrieves data without modifying state.
Register the Veroq MCP server in PolicyLayer and add a rule for veroq_crypto: 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 Veroq. Nothing to install.
veroq_crypto 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 veroq_crypto 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 veroq_crypto. 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.
veroq_crypto is provided by the Veroq MCP server (veroq-ai/veroq-mcp). 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 →